o B]G@sddlmZddlmZddlmZgdZGdddeZej Z ej Z ej Z ej Z ej Z ejZ ejZ ejZ ejZ ejZ ejZ ejZ ejZ ejZ ejZ ejZ ejZ ejZ GdddeZd S) )config)error)null) CommunityData UsmUserDatausm3DESEDEPrivProtocolusmAesCfb128ProtocolusmAesCfb192ProtocolusmAesCfb256ProtocolusmAesBlumenthalCfb192ProtocolusmAesBlumenthalCfb256ProtocolusmDESPrivProtocolusmHMACMD5AuthProtocolusmHMACSHAAuthProtocolusmHMAC128SHA224AuthProtocolusmHMAC192SHA256AuthProtocolusmHMAC256SHA384AuthProtocolusmHMAC384SHA512AuthProtocolusmNoAuthProtocolusmNoPrivProtocolc@sXeZdZdZdZedZdZeZeZ   d ddZ ddZ d d Z   dd d Z dS)ra Creates SNMP v1/v2c configuration entry. This object can be used by :py:class:`~pysnmp.hlapi.asyncore.AsyncCommandGenerator` or :py:class:`~pysnmp.hlapi.asyncore.AsyncNotificationOriginator` and their derivatives for adding new entries to Local Configuration Datastore (LCD) managed by :py:class:`~pysnmp.hlapi.SnmpEngine` class instance. See :RFC:`2576#section-5.3` for more information on the *SNMP-COMMUNITY-MIB::snmpCommunityTable*. Parameters ---------- communityIndex: :py:class:`str`, :py:class:`~pysnmp.proto.rfc1902.OctetString` Unique index value of a row in snmpCommunityTable. If it is the only positional parameter, it is treated as a *communityName*. communityName: :py:class:`str`, :py:class:`~pysnmp.proto.rfc1902.OctetString` SNMP v1/v2c community string. mpModel: :py:class:`int` SNMP message processing model AKA SNMP version. Known SNMP versions are: * `0` - for SNMP v1 * `1` - for SNMP v2c (default) contextEngineId: :py:class:`str`, :py:class:`~pysnmp.proto.rfc1902.OctetString` Indicates the location of the context in which management information is accessed when using the community string specified by the above communityName. contextName: :py:class:`str`, :py:class:`~pysnmp.proto.rfc1902.OctetString` The context in which management information is accessed when using the above communityName. tag: :py:class:`str` Arbitrary string that specifies a set of transport endpoints from which a command responder application will accept management requests with given *communityName* or to which notification originator application will send notifications when targets are specified by a tag value(s). The other way to look at the *tag* feature is that it can make specific *communityName* only valid for certain targets. The other use-case is when multiple distinct SNMP peers share the same *communityName* -- binding each instance of *communityName* to transport endpoint lets you distinguish SNMP peers from each other (e.g. resolving *communityName* into proper *securityName*). For more technical information on SNMP configuration tags please refer to :RFC:`3413#section-4.1.1` and :RFC:`2576#section-5.3` (e.g. the *snmpCommunityTransportTag* object). See also: :py:class:`~pysnmp.hlapi.UdpTransportTarget` Warnings -------- If the same *communityIndex* value is supplied repeatedly with different *communityName* (or other parameters), the later call supersedes all previous calls. Make sure not to configure duplicate *communityName* values unless they have distinct *mpModel* and/or *tag* fields. This will make *communityName* based database lookup ambiguous. Examples -------- >>> from pysnmp.hlapi import CommunityData >>> CommunityData('public') CommunityData(communityIndex='s1410706889', communityName=, mpModel=1, contextEngineId=None, contextName='', tag='') >>> CommunityData('public', 'public') CommunityData(communityIndex='public', communityName=, mpModel=1, contextEngineId=None, contextName='', tag='') >>>  noAuthNoPrivNcCs|dur ||_|d|_||_|dur||_|dur||_|dur&|d}}||_|durCdt|j|j|j|j|jf|_|_dS||_|durL|pM||_dS)Nrzs%s) mpModel securityModelcontextEngineId contextNametag communityNamehashcommunityIndex securityNameselfrrrrrrr r#3/usr/lib/python3/dist-packages/pysnmp/hlapi/auth.py__init__ls&   zCommunityData.__init__cCtd|jjNz%s is not hashable TypeError __class____name__r"r#r#r$__hash__zCommunityData.__hash__cCs&d|jj|j|j|j|j|j|jfS)Nzy%s(communityIndex=%r, communityName=, mpModel=%r, contextEngineId=%r, contextName=%r, tag=%r, securityName=%r))r*r+rrrrrr r,r#r#r$__repr__szCommunityData.__repr__c Cs||dur |d}}|||dur|jp||dur|jp||dur#|jp$||dur+|jp,||dur3|jp4||dur;|jp<|SN)r*rrrrrr r!r#r#r$clones zCommunityData.clone)NNNNNN)NNNNNNN)r+ __module__ __qualname____doc__rr securityLevelrrrr%r-r/r1r#r#r#r$rs"O  rc@sreZdZdZdZZejZej Z dZ dZ dZ eZddddddeefddZddZd d Z     d d d ZdS)raCreates SNMP v3 User Security Model (USM) configuration entry. This object can be used by :py:class:`~pysnmp.hlapi.asyncore.AsyncCommandGenerator` or :py:class:`~pysnmp.hlapi.asyncore.AsyncNotificationOriginator` and their derivatives for adding new entries to Local Configuration Datastore (LCD) managed by :py:class:`~pysnmp.hlapi.SnmpEngine` class instance. See :RFC:`3414#section-5` for more information on the *SNMP-USER-BASED-SM-MIB::usmUserTable*. Parameters ---------- userName: :py:class:`str`, :py:class:`~pysnmp.proto.rfc1902.OctetString` A human readable string representing the name of the SNMP USM user. Other Parameters ---------------- authKey: :py:class:`str`, :py:class:`~pysnmp.proto.rfc1902.OctetString` Initial value of the secret authentication key. If not set, :py:class:`~pysnmp.hlapi.usmNoAuthProtocol` is implied. If set and no *authProtocol* is specified, :py:class:`~pysnmp.hlapi.usmHMACMD5AuthProtocol` takes effect. privKey: :py:class:`str`, :py:class:`~pysnmp.proto.rfc1902.OctetString` Initial value of the secret encryption key. If not set, :py:class:`~pysnmp.hlapi.usmNoPrivProtocol` is implied. If set and no *privProtocol* is specified, :py:class:`~pysnmp.hlapi.usmDESPrivProtocol` takes effect. authProtocol: :py:class:`tuple`, :py:class:`~pysnmp.proto.rfc1902.ObjectIdentifier` An indication of whether messages sent on behalf of this USM user can be authenticated, and if so, the type of authentication protocol which is used. Supported authentication protocol identifiers are: * :py:class:`~pysnmp.hlapi.usmNoAuthProtocol` (default is *authKey* not given) * :py:class:`~pysnmp.hlapi.usmHMACMD5AuthProtocol` (default if *authKey* is given) * :py:class:`~pysnmp.hlapi.usmHMACSHAAuthProtocol` * :py:class:`~pysnmp.hlapi.usmHMAC128SHA224AuthProtocol` * :py:class:`~pysnmp.hlapi.usmHMAC192SHA256AuthProtocol` * :py:class:`~pysnmp.hlapi.usmHMAC256SHA384AuthProtocol` * :py:class:`~pysnmp.hlapi.usmHMAC384SHA512AuthProtocol` securityEngineId: :py:class:`~pysnmp.proto.rfc1902.OctetString` The snmpEngineID of the authoritative SNMP engine to which a dateRequest message is to be sent. Will be automatically discovered from peer if not given, unless localized keys are used. In the latter case *securityEngineId* must be specified. See :RFC:`3414#section-2.5.1` for technical explanation. securityName: :py:class:`str`, :py:class:`~pysnmp.proto.rfc1902.OctetString` Together with the snmpEngineID it identifies a row in the *SNMP-USER-BASED-SM-MIB::usmUserTable* that is to be used for securing the message. See :RFC:`3414#section-2.5.1` for technical explanation. privProtocol: :py:class:`tuple`, :py:class:`~pysnmp.proto.rfc1902.ObjectIdentifier` An indication of whether messages sent on behalf of this USM user be encrypted, and if so, the type of encryption protocol which is used. Supported encryption protocol identifiers are: * :py:class:`~pysnmp.hlapi.usmNoPrivProtocol` (default is *authKey* not given) * :py:class:`~pysnmp.hlapi.usmDESPrivProtocol` (default if *authKey* is given) * :py:class:`~pysnmp.hlapi.usm3DESEDEPrivProtocol` * :py:class:`~pysnmp.hlapi.usmAesCfb128Protocol` * :py:class:`~pysnmp.hlapi.usmAesCfb192Protocol` * :py:class:`~pysnmp.hlapi.usmAesCfb256Protocol` authKeyType: :py:class:`int` Type of `authKey` material. See :RFC:`3414#section-2.6` for technical explanation. Supported key types are: * :py:class:`~pysnmp.hlapi.usmKeyTypePassphrase` (default) * :py:class:`~pysnmp.hlapi.usmKeyTypeMaster` * :py:class:`~pysnmp.hlapi.usmKeyTypeLocalized` privKeyType: :py:class:`int` Type of `privKey` material. See :RFC:`3414#section-2.6` for technical explanation. Supported key types are: * :py:class:`~pysnmp.hlapi.usmKeyTypePassphrase` (default) * :py:class:`~pysnmp.hlapi.usmKeyTypeMaster` * :py:class:`~pysnmp.hlapi.usmKeyTypeLocalized` Notes ----- 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. 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 -------- >>> from pysnmp.hlapi import UsmUserData >>> UsmUserData('testuser', authKey='authenticationkey') UsmUserData(userName='testuser', authKey=, privKey=, authProtocol=(1,3,6,1,6,3,10,1,1,2), privProtocol=(1,3,6,1,6,3,10,1,2,1)) >>> UsmUserData('testuser', authKey='authenticationkey', privKey='encryptionkey') UsmUserData(userName='testuser', authKey=, privKey=, authProtocol=(1,3,6,1,6,3,10,1,1,2), privProtocol=(1,3,6,1,6,3,10,1,2,2)) >>> Nrc Cs||_|dur ||_n||_|dur)||_|durtj|_n||_|jdkr)d|_|durJ||_|jtjkr;t dd|_|durGtj |_ n||_ ||_ ||_| |_dS)NZauthPrivZ authNoPrivzPrivacy implies authenticity)userNamer authKeyrr authProtocolr5privKeyrrZ PySnmpErrorr privProtocolsecurityEngineId authKeyType privKeyType r"r7r8r:r9r;r<r r=r>r#r#r$r%`s,      zUsmUserData.__init__cCr&r'r(r,r#r#r$r-r.zUsmUserData.__hash__c Cs8d|jj|j|j|j|jdurdp|j|j|j|jfS)Nz%s(userName=%r, authKey=, privKey=, authProtocol=%r, privProtocol=%r, securityEngineId=%r, securityName=%r, authKeyType=%r, privKeyType=%r)z ) r*r+r7r9r;r<r r=r>r,r#r#r$r/szUsmUserData.__repr__c Cs||dur |jp ||dur|jp||dur|jp||dur!|jp"||dur)|jp*||dur1|jp2||dur9|jp:||durA|jpBt | durI|j pJt Sr0) r*r7r8r:r9r;r<r r=usmKeyTypePassphraser>r?r#r#r$r1szUsmUserData.clone) NNNNNNNNN)r+r2r3r4r8r:rrr9rr;r5rrrrr@r%r-r/r1r#r#r#r$rs0} $ rN)Z pysnmp.entityrZpysnmprZpyasn1.compat.octetsr__all__objectrrrrrrrrrr rrr r r r r@ZusmKeyTypeMasterZusmKeyTypeLocalizedrr#r#r#r$sV