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

Implement RFC-3411 (for SNMPv3 and SNMPv1 support) #84

Closed
exhuma opened this issue Jul 20, 2020 · 3 comments
Closed

Implement RFC-3411 (for SNMPv3 and SNMPv1 support) #84

exhuma opened this issue Jul 20, 2020 · 3 comments
Labels

Comments

@exhuma
Copy link
Owner

exhuma commented Jul 20, 2020

Issue Description

RFC-3411 outlines a recommended architecture for SNMP applications. The architecture aims to be future-proof and allows for easier extension.

It most importantly allows better and cleaner support for both SNMPv1, SNMPv2 and SNMPv3 with a shared code-base.

Implementing this architecture would be a stepping stone for SNMPv3 support and would also allow us to tackle #3 for better transport-level settings like timeouts.

@exhuma exhuma added the v1.x label May 19, 2022
@forrejam
Copy link

forrejam commented Jun 2, 2022

Just wondering what are the blockers for v3 support and if could start to help in that area? is there anywhere tracking what needs to be done or potential issues with implementing v3 support?

@exhuma
Copy link
Owner Author

exhuma commented Jun 2, 2022

There's a release candidate out with SNMPv3 support. https://pypi.org/project/puresnmp/#history

You can install it by either pinning the version: pip install "puresnmp==2.0.0rc6" or activating the --pre flag: pip install --pre puresnmp

If you need DES and AES encryption you need to activate the crypto extra: pip install puresnmp[crypto]. It is packaged separately so applications that don't need encryption don't need to pull in those dependencies.

As this is a major upgrade, I strongly suggest looking at the docs: https://puresnmp.readthedocs.io/en/develop/

@exhuma
Copy link
Owner Author

exhuma commented Jun 2, 2022

Considering that it is implemented I will close this. The RC has been in use for quite a while already and it qualifies as a full release. I am planning to do that in the coming days.

@exhuma exhuma closed this as completed Jun 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants