You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?
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.
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.
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.
The text was updated successfully, but these errors were encountered: