summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Release 4.4.12v4.4.12release-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/+116
|
* Docstring fixIlya Etingof2019-08-111-5/+5
|
* Prepare for 4.4.12Ilya Etingof2019-08-112-1/+6
|
* Release 4.4.11v4.4.11release-4.4.11Ilya Etingof2019-08-111-1/+1
|
* Fix crash on AES key localizationIlya Etingof2019-08-111-1/+2
|
* Introduce "wildcard" SNMP engine ID (#297)Ilya Etingof2019-08-112-30/+73
| | | | | | | | | | 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-102-2/+8
|
* Move most of SNMP engine discovery code to security moduleIlya Etingof2019-08-063-29/+50
| | | | | | | | | | | | | 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-051-6/+6
|
* Fix USM configuration for the case of partial keysIlya Etingof2019-08-041-9/+13
|
* Do not store incomplete USM keys and improve USM debuggingIlya Etingof2019-08-044-38/+172
| | | | | | | | | | | | | 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-1/+1
|
* Add USM master and localized keys configuration support (#295)Ilya Etingof2019-08-039-46/+184
| | | | | | | | | | | 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.
* Prepare for 4.4.11Ilya Etingof2019-08-012-1/+6
|
* Make received MIB objects resolution more forgivingv4.4.10release-4.4.10Ilya Etingof2019-07-303-13/+23
| | | | | | | | | 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-5/+21
| | | | | 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-292-2/+2
|
* Fix Python 2.5 compatibilityIlya Etingof2019-07-291-2/+2
| | | | @property.setter has not been invented back then
* Fix Python 2.4 compatibilityIlya Etingof2019-07-291-8/+15
| | | | @property.setter has not been invented back then
* Rework VACM access control function (#287)Ilya Etingof2019-07-295-119/+508
| | | | | | | | 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-202-12/+14
| | | | | Fixed crash on uninitialized component serialization left out in SNMP v1 TRAP PDU to SNMPv2/3 TRAP PDU translation routine.
* Fix `var-bindings` initializationIlya Etingof2019-06-233-3/+9
| | | | | | | 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-012-19/+33
|
* Update periodics call interval on timer resolution changeIlya Etingof2019-03-312-1/+17
| | | | | Fix to updates call interval of the existing periodic dispatcher jobs on call interval change (via .setTimerResolution())
* Respect timer resolution in asyncore main loopIlya Etingof2019-03-312-3/+3
| | | | | Fixes asyncore main loop upper bound timeout to respect currently set timer resolution.
* Prepare for 4.4.10Ilya Etingof2019-02-092-1/+6
|
* Release 4.4.9v4.4.9Ilya Etingof2019-02-091-2/+2
|
* Add missing SNMP PDU error classesIlya Etingof2019-02-084-14/+70
| | | | | Added missing SNMP PDU error classes and their handling in Command Responder
* Fix IPV6_TRANSPARENT socket optionIlya Etingof2019-01-143-2/+5
|
* Do not set IP_PKTINFO socket option on IPv6 socketIlya Etingof2019-01-122-4/+3
| | | | | Trying to understand why sendmsg() fails on a transparent IPv6 socket
* Improve IPV6 debuggingIlya Etingof2019-01-112-4/+12
|
* Fix socket iov blob dump in debugIlya Etingof2019-01-111-3/+5
|
* Add `IPV6_V6ONLY` IPV6 socket optionIlya Etingof2019-01-102-2/+3
| | | | SO says this is required for proper UDP socket multi-homing.
* Emit low-level sendmsg/recvmsg debuggingIlya Etingof2019-01-102-0/+28
| | | | | When running in transparent proxy mode, log syscall parameters to aid troubleshooting
* MIB loader ignores file and directory access errorsIlya Etingof2019-01-082-10/+15
| | | | | Also fixed crash on MIB load failure in case of directory access error
* Prepare for 4.4.9Ilya Etingof2019-01-082-1/+6
|
* Release 4.4.8v4.4.8Ilya Etingof2018-12-301-1/+1
|
* Fix Pythonized MIB load in source formIlya Etingof2018-12-302-22/+36
|
* Prepare for 4.4.8Ilya Etingof2018-12-302-1/+6
|
* Release 4.4.7v4.4.7Ilya Etingof2018-12-301-1/+1
|
* Fix undefined names in `TRANSPORT-ADDRESS-MIB.py`Ilya Etingof2018-12-302-3/+5
|
* Extend copyright notice to year 2019Ilya Etingof2018-12-29144-144/+145
|
* Switch Travis CI to TrustyIlya Etingof2018-12-291-18/+20
|
* Fix wrong `set()` member deletion in `MibBuilder`Ilya Etingof2018-12-251-2/+2
|
* Fix possible duplicate key condition in `OrderedDict`Ilya Etingof2018-12-252-37/+40
| | | | | Also, updated thr `.update` and `__init__` methods signatures to match `dict` interface. Implementation details renewed.
* Disable Travis builds for py 2.6, 3.2 & 3.3Ilya Etingof2018-11-031-12/+0
| | | | Seems like they discontinued those.
View Lorry Controller Status