Skip to content
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

$snmpv2_enable parameter does not disable snmpv2. #275

Open
prouveyrol opened this issue Jul 21, 2023 · 0 comments
Open

$snmpv2_enable parameter does not disable snmpv2. #275

prouveyrol opened this issue Jul 21, 2023 · 0 comments

Comments

@prouveyrol
Copy link

Hello,
I have been looking for a way to use this module to enable snmpv3 only on some servers.
I found #56 which proposes a merged PR that prevents related entries in the VACM configuration.

I also found that one way to prevent the use of snmpv2 with cleartext community name is to remove these lines from Traditional Access Control

rocommunity public 127.0.0.1/32
rocommunity6 public ::1/128

This is however not done by the $snmpv2_enable => false parameter. And if the parameter ro_community is left undefined, it defaults to public. I have not found a way to not generate these lines with this module as it is, hence no way to disable snmp v1 and v2c.

Am I missing something obvious here?

Currently, my workaround is to use a huge random community string. I may try to provide a PR if I find the time for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant