The PEM file created when generating one with znc --makeconf uses potentially unsafe permissions. On many systems, the default permissions are 644 or 664 (Ubuntu). This can lead to key compromise on shared systems like shell boxes.
Proposed fix: Ensure znc.pem is chmod 600.
The PEM file created when generating one with znc --makeconf uses potentially unsafe permissions. On many systems, the default permissions are 644 or 664 (Ubuntu). This can lead to key compromise on shared systems like shell boxes.
Proposed fix: Ensure znc.pem is chmod 600.
<!-- github-sync-id:16195456 -->
It's already fixed for the file itself. Use git or 1.2a version
And even in 1.0, .znc directory itself is 700 by default, which stops world to read znc.pem
It's already fixed for the file itself. Use git or 1.2a version
And even in 1.0, .znc directory itself is 700 by default, which stops world to read znc.pem
<!-- github-comment-id:20262441 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The PEM file created when generating one with znc --makeconf uses potentially unsafe permissions. On many systems, the default permissions are 644 or 664 (Ubuntu). This can lead to key compromise on shared systems like shell boxes.
Proposed fix: Ensure znc.pem is chmod 600.
root@vps6431:
# znc --makepem# stat .znc/znc.pem[ ok ] Writing Pem file [/root/.znc/znc.pem]...
root@vps6431:
File: ‘.znc/znc.pem’
Size: 2993 Blocks: 8 IO Block: 4096 regular file
Device: ca01h/51713d Inode: 1753104 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2013-07-01 01:16:29.000000000 +0000
Modify: 2013-07-01 01:16:29.000000000 +0000
Change: 2013-07-01 01:16:29.000000000 +0000
Birth: -
root@vps6431:~#
It's already fixed for the file itself. Use git or 1.2a version
And even in 1.0, .znc directory itself is 700 by default, which stops world to read znc.pem