summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorIlya Etingof <etingof@gmail.com>2019-08-11 12:40:03 +0200
committerIlya Etingof <etingof@gmail.com>2019-08-11 12:42:41 +0200
commit0584598a682326f1d7bd6abc7aba2a3eca350011 (patch)
tree2f1f8cf854a2d94ec4179ecd5be4738934d77c77
parent496f19889693f5b0ef299aecb17e18d4aa037479 (diff)
downloadpysnmp-git-0584598a682326f1d7bd6abc7aba2a3eca350011.tar.gz
Docstring fix
-rw-r--r--pysnmp/hlapi/v3arch/auth.py10
1 files changed, 5 insertions, 5 deletions
diff --git a/pysnmp/hlapi/v3arch/auth.py b/pysnmp/hlapi/v3arch/auth.py
index d93e30af..34609904 100644
--- a/pysnmp/hlapi/v3arch/auth.py
+++ b/pysnmp/hlapi/v3arch/auth.py
@@ -343,11 +343,11 @@ class UsmUserData(object):
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*.
+ If :py:class:`~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.