diff options
| author | Ilya Etingof <etingof@gmail.com> | 2019-08-06 23:35:59 +0200 |
|---|---|---|
| committer | Ilya Etingof <etingof@gmail.com> | 2019-08-11 00:17:19 +0200 |
| commit | cdd1921128b30e76201b8fc12a78197490780f9f (patch) | |
| tree | f454504d36abd6da2a2f43f7873daeeca58225f8 /pysnmp/hlapi/auth.py | |
| parent | c351e90391b7772c3d93e63b64d479cae5f44f6b (diff) | |
| download | pysnmp-git-wildcard-engine-id.tar.gz | |
Introduce "wildcard" SNMP engine IDwildcard-engine-id
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?
Diffstat (limited to 'pysnmp/hlapi/auth.py')
| -rw-r--r-- | pysnmp/hlapi/auth.py | 20 |
1 files changed, 15 insertions, 5 deletions
diff --git a/pysnmp/hlapi/auth.py b/pysnmp/hlapi/auth.py index e784eec8..735d85df 100644 --- a/pysnmp/hlapi/auth.py +++ b/pysnmp/hlapi/auth.py @@ -305,11 +305,6 @@ class UsmUserData(object): * :py:class:`~pysnmp.hlapi.usmKeyTypeMaster` * :py:class:`~pysnmp.hlapi.usmKeyTypeLocalized` - - If `~pysnmp.hlapi.usmKeyTypeLocalized` is used, peer SNMP engine ID - discovery mechanism can't be leveraged for key localization, so - *securityEngineId* must be given by local configuration. - privKeyType: :py:class:`int` Type of `privKey` material. See :RFC:`3414#section-2.6` for technical explanation. @@ -320,6 +315,21 @@ class UsmUserData(object): * :py:class:`~pysnmp.hlapi.usmKeyTypeMaster` * :py:class:`~pysnmp.hlapi.usmKeyTypeLocalized` + Notes + ----- + If `~pysnmp.hlapi.usmKeyTypeLocalized` is used when running a + non-authoritative SNMP engine, USM key localization mechanism + is not invoked. As a consequence, local SNMP engine configuration + won't get automatically populated with remote SNMP engine's + *securityEngineId*. + + Therefore peer SNMP engine's *securityEngineId* must be added + to local configuration and associated with its localized keys. + + Alternatively, the magic *securityEngineId* value of five zeros + (*0x0000000000*) can be used to refer to the localized keys that + should be used with any unknown remote SNMP engine. This feature + is specific to pysnmp. Examples -------- |