-
-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File permissions do not match the ones of the net-snmp #81
Comments
@Tontonitch I'm not a developer of puppet-snmp, but a fellow user. Good catch here given this file has credentials stored that should be kept secret and protected. It seems that the Red Hat family of OSes have the wrong default mode for these files, as you can see here. Until this gets resolved correctly, I've got the following in my Hiera data:
Thanks for pointing this out! |
Ok, thanks for your solution John!Best regards,Yannick
À : razorsedge/puppet-snmp puppet-snmp@noreply.github.com @Tontonitch I'm not a developer of puppet-snmp, but a fellow user. Good catch here given this file has credentials stored that should be kept secret and protected. It seems that the Red Hat family of OSes have the wrong default mode for these files, as you can see here.Until this gets resolved correctly, I've got the following in my Hiera data: Alternatively, you could use something likeclass { 'snmp': |
Please make this a parameter. We have certain machines that set the file perms to 0640 and the group to something non-standard. (Rationale: Certain processes need to read that file but we don't want those processes to run as root) |
It already is a parameter. See my comment above. Or I don't understand what you were asking for.John Florian |
Its all good. Thanks! |
@Tontonitch What OS/OS version/SNMP version are you using? |
RedHat 7.3, Net-Snmp 5.7.2 |
Hi,
After configuring the snmp services via your puppet module, the permissions of the following files do not match the ones of the net-snmp software rpm.
The puppet module sets the perm to 644 instead of 600.
Could it be changed in a future release of the module?
So that I won't receive any alerts in reports from SCAP.
Best regards,
Yannick
The text was updated successfully, but these errors were encountered: