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

USM user entry will be overridden while adding v3 user for traps #137

Open
heisenberg-7 opened this issue Oct 23, 2024 · 2 comments
Open
Labels
area:pysnmp PySNMP package priority:low Low priority items. question Further information is requested

Comments

@heisenberg-7
Copy link

heisenberg-7 commented Oct 23, 2024

I noticed that pysnmpUsmSecretEntry is stored/fetched on basis on security name which can be same for two different devices with same user but only difference being engine-id, so if we add two users (say user 1 and user 2) with user having same username and security name but different engine-id and credentials for auth protocol and priv protocol, only last added user's entry (say user 2) will be available in pysnmpUsmSecretEntry so will that cause any issue in processing of traps from user 1?
Ref:
https://github.com/lextudio/pysnmp/blob/main/pysnmp/entity/config.py#L217
https://github.com/lextudio/pysnmp/blob/main/pysnmp/entity/config.py#L340

@lextudio-support
Copy link

New issues are marked as low priority by default. Becoming our commercial customers, and then your reports are handled with higher priority after triage.

@lextudio-support lextudio-support added area:pysnmp PySNMP package priority:low Low priority items. question Further information is requested labels Oct 23, 2024
@heisenberg-7
Copy link
Author

@lextm any input on above?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:pysnmp PySNMP package priority:low Low priority items. question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants