Release 4.4.12 #437
Open
Release 4.4.12 #437
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
* asyncio.async deprecated since 3.4.4
Python 3.7 was just released [1]. This is a small change to enable support in pysnmp. [1] https://docs.python.org/3.7/whatsnew/3.7.html Signed-off-by: Eric Brown <browne@vmware.com>
It appears that Python 3.7 use in Travis-CI is finally fixed. However, it requires use of xenial distribution and sudo: true. Those have now been added to the matrix. Signed-off-by: Eric Brown <browne@vmware.com>
Probably introduced by commit 2b27b49
This reverts commit 23d1aa7.
…#175) Otherwise, they are likely to use the system python.
As async is the keyword since Python 3.7, let's use gettattr built-in function to call async function from asyncio.
Fixed crash caused by incoming SNMPv3 message requesting SNMPv1/v2c security model
Fixed out-of-scope OIDs possibly leaking at the end of SNMP table at hlapi `nextCmd` and `bulkCmd` calls when `lexicographicMode = False`.
To convey parent exception information on re-raise
Fixes asyncore main loop upper bound timeout to respect currently set timer resolution.
Fix to updates call interval of the existing periodic dispatcher jobs on call interval change (via .setTimerResolution())
Also fixes bug in `imp`-based initialization
Set `var-bindings` to an empty sequence by default. Otherwise it can remain a "pyasn1 schema object" failing to encode. This can happen with newer pyasn1 versions where `SequenceOf` type does not have default initializer.
Fixed crash on uninitialized component serialization left out in SNMP v1 TRAP PDU to SNMPv2/3 TRAP PDU translation routine.
Most important changes include: * Added subtree match negation support (vacmViewTreeFamilyType) * Added subtree family mask support (vacmViewTreeFamilyMask) * Added prefix content name matching support (vacmAccessContextMatch) * Added key VACM tables caching for better lookup performance
@property.setter has not been invented back then
@property.setter has not been invented back then
This fixes release 4.4.10 before it's actually released.
Added optional `ignoreErrors` parameter to `ObjectType.resolveWithMib()` to control that behaviour.
Previously, MIB resolution errors were ignored (whenever possible) for objects we were sending and receiving. This change tightens outgoing objects MIB compliance (send will fail), but tolerate non quite compliant objects we receive. Also, extend the same policy onto `NotificationOriginator`.
Added new optional parameters to `addUsmUser()` and `hlapi.UsmUserData()` functions allowing specifying key material type being passed to the respective routines. Plain-text pass-phrase remains the default, while user can change that to `master` or `localized` types. Refer to RFC3414 for technical details on SNMP USM key localization algorithm.
This adds details debugging on USM initial configuration process and runtime USM user cloning. Besides that, this patch eliminates storing of incomplete USM keys (in case when master/localized keys are configured directly). On top of that, this commit fixes a bug in USM configuration which did not allow the same user names to be added under different security names.
This SNMP engine ID discovery procedure is spread across message processing and security modules. This is weird! Anyway, this change moves SNMP message rewriting, associated with starting out SNMP discovery sequence, to security module. The motivation is to let security module making the ultimate decision whether or not SNMP engine discovery is required. For example, if localized keys are committed directly to the DB, security module may just use them without engine discovery phase.
This change introduces "wildcard" SNMP engine ID (0x00000000). Right before deciding on firing up SNMP engine ID discovery and key localization procedure, originating SNMP engine will check for the presence of this magical engine ID (5 zeros), if it is present in LCD along with the user name being used, localized keys from that entry will be used. Does this have security implications?
Fixed a regression in SNMPv3 `msgFlag` initialization on authoritative SNMP engine ID discovery. This bug causes secure communication with peer SNMP engines to stall at SNMP engine ID discovery procedure.
|
What you typed is clearly a question, and a general question applicable to all Python packages (not only PySNMP). That is not usually suitable to be posted on a GitHub repo like this, but should go to a Python centric forum. BTW, read #429 to learn why posting in this repo isn't a good idea any more as its owner is no longer with us. |
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.
How can I install this module on a windows server that has no internet access?