When using SNMPv3, userName always needs to be set. #68
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 3 commits
November 27, 2020 10:05
See https://tools.ietf.org/html/rfc3414#section-3.1, point 7: userName is set into the trap even when securityLevel = NoAuthNoPriv Dependency "github.com/k-sone/snmpgo" is returning an error when username is not set
|
Thanks for you contribution |
|
I just released the 1.1.1 version with your fix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After testing the latest release, I noticed that my previous PR was incomplete. SNMPv3 username need to be set even if authentication is disabled (NoAuthNoPriv use case). This PR address this.
This fix was tested with a locally built container and it is working correctly.