summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Update FUNDING.ymlHEADmasterIlya Etingof2019-12-151-1/+1
|
* Add SNMP agent with multiple SNMP context example scriptIlya Etingof2019-11-122-0/+87
|
* Improve the setuptools version check (#322)Michael Weiss2019-11-071-1/+1
| | | Handles malformed `setuptools.__version__` such as "41.4.0.post20191022"
* Travis CI: Add Python 3.8 (#321)Christian Clauss2019-11-062-35/+14
| | | Travis CI: Add Python 3.8
* Fix typo in docstringIlya Etingof2019-09-261-2/+2
|
* Release 4.4.12Ilya Etingof2019-09-241-1/+1
|
* Fix broken SNMPv3 authoritative engine ID discoveryIlya Etingof2019-09-243-4/+6
| | | | | | | 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.
* Add examples on master&localized keys useIlya Etingof2019-08-133-0/+126
|
* Docstring fixIlya Etingof2019-08-111-5/+5
|
* Prepare for 4.4.12Ilya Etingof2019-08-111-0/+5
|
* Release 4.4.11Ilya Etingof2019-08-111-2/+2
|
* Fix crash on AES key localizationIlya Etingof2019-08-111-1/+2
|
* Introduce "wildcard" SNMP engine ID (#297)Ilya Etingof2019-08-112-29/+74
| | | | | | | | | | | 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?
* Pin Twisted on Python < 3.5Ilya Etingof2019-08-101-1/+2
|
* Move SNMP engine discovery code to security moduleIlya Etingof2019-08-103-32/+49
| | | | | | | | | | | | | 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.
* Fix crashing VACM debuggingIlya Etingof2019-08-101-4/+4
|
* Expose USM_* constants to `hlapi` top-level scopeIlya Etingof2019-08-053-60/+105
|
* Fix USM configuration for the case of partial keysIlya Etingof2019-08-051-1/+1
|
* Fix malformed OBJECT-TYPE MAX-ACCESS constantsIlya Etingof2019-08-053-13/+13
|
* Do not store incomplete USM keys and improve debugIlya Etingof2019-08-055-39/+166
| | | | | | | | | | | | | 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.
* Add missing enumeration to `pysnmpUemKeyType`Ilya Etingof2019-08-041-36/+35
|
* Add USM master and localized keys configuration support (#295)Ilya Etingof2019-08-0310-75/+267
| | | | | | | | | | | | 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.
* Add more time (90 mins) for test scripts to runIlya Etingof2019-07-311-1/+1
| | | | /me is hopeful to migrate to local tests
* Prepare for 4.4.11Ilya Etingof2019-07-311-0/+5
|
* Use SPDX identifier to specify the exact license type (#291)Yegor Yefremov2019-07-311-1/+1
|
* Do not run asyncio examples under Python < 3.3Ilya Etingof2019-07-301-1/+1
|
* Fix wrong cherry-picked debug flagIlya Etingof2019-07-301-1/+1
|
* Make received MIB objects resolution more forgivingIlya Etingof2019-07-303-11/+21
| | | | | | | | | 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`.
* Make MIB objects resolution more forgivingIlya Etingof2019-07-302-6/+24
| | | | | Added optional `ignoreErrors` parameter to `ObjectType.resolveWithMib()` to control that behaviour.
* Support various forms of `vacmViewTreeFamilyMask` inputIlya Etingof2019-07-301-1/+1
| | | | This fixes release 4.4.10 before it's actually released.
* Release 4.4.10Ilya Etingof2019-07-302-2/+2
|
* Rework VACM access control function (#287)Ilya Etingof2019-07-295-102/+494
| | | | | | | | | 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
* Fix TRAP PDU proxy translationIlya Etingof2019-07-262-14/+14
| | | | | Fixed crash on uninitialized component serialization left out in SNMP v1 TRAP PDU to SNMPv2/3 TRAP PDU translation routine.
* Update FUNDING.ymlIlya Etingof2019-07-071-1/+1
|
* Create FUNDING.ymlIlya Etingof2019-07-041-0/+1
|
* Fix `var-bindings` initializationIlya Etingof2019-06-233-3/+10
| | | | | | | 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.
* Fix `importlib` use on Py27Ilya Etingof2019-04-121-5/+11
| | | | Also fixes bug in `imp`-based initialization
* Replace `imp` with `importlib` is availableIlya Etingof2019-04-022-23/+34
|
* Fix SNMP version in Twisted example (#246)Jorge Cabrera2019-03-051-1/+1
|
* Fix `MibBuilder.loadModules()` no respect missing MIB failureIlya Etingof2019-02-271-13/+15
| | | | | Missing MIB condition has been ignored if MIB compiler is not configured.
* Fix missing variable references in SMI instrumentationIlya Etingof2019-02-261-0/+4
|
* Drop legacy `pysnmp.carrier.asynsock`Ilya Etingof2019-02-264-31/+0
| | | | | The sub-package is now known under the name `asyncore` because of the presence of many other event loops.
* PEP-8 long lines and dunders (#245)Ilya Etingof2019-02-2688-2308/+3846
| | | | This patch massively reformats the whole codebase mainly wrapping long lines and eliminating dundered private attributes.
* Skip tests requiring broadcast featureIlya Etingof2019-02-251-1/+1
|
* Fix some ntforg example scripts not using trapOIDIlya Etingof2019-02-252-2/+2
|
* Fix failing example scriptsIlya Etingof2019-02-255-7/+9
|
* Fix PDU consistency check in notification originatorIlya Etingof2019-02-254-7/+7
|
* Fix variable reference in hlapi/v1arch/ntforgIlya Etingof2019-02-251-2/+2
|
* Include missing `hlapi.v1arch` subpackage in `setup.py`Ilya Etingof2019-02-251-0/+1
|
* Ensure TRAP PDU consistency in v1archIlya Etingof2019-02-235-114/+186
| | | | | | Also, consistency ensuring code unified with v3arch piece what has the side effect of *requiring* snmpTrapOID to be always present anywhere among user-supplied variable-bindings.
View Lorry Controller Status