a ai%@sddlmZddlmZddlZddlZddlZddl m Z ddl m Z ddl m Z ddl m Z ddlmZGd d d ZGd d d eZddddddZGdddeZdddddZGdddZdS)) annotationsN)_base64_alphabet) base64_decode) base64_encode want_bytes) BadSignaturec@s6eZdZdZddddddZddddddd Zd S) SigningAlgorithmzgSubclasses must implement :meth:`get_signature` to provide signature generation functionality. byteskeyvaluereturncCs tdS)z2Returns the signature for the given key and value.N)NotImplementedErrorselfr rrM/var/www/html/SiteWeb/venv/lib/python3.9/site-packages/itsdangerous/signer.py get_signatureszSigningAlgorithm.get_signaturebool)r rsigrcCst||||S)zMVerifies the given signature matches the expected signature. )hmaccompare_digestr)rr rrrrrverify_signaturesz!SigningAlgorithm.verify_signatureN)__name__ __module__ __qualname____doc__rrrrrrr sr c@s"eZdZdZddddddZdS) NoneAlgorithmz`Provides an algorithm that does not perform any signing and returns an empty signature. r r cCsdS)Nrrrrrr$szNoneAlgorithm.get_signatureN)rrrrrrrrrrsrr r t.Any)stringrcCs t|S)zDon't access ``hashlib.sha1`` until runtime. FIPS builds may not include SHA-1, in which case the import and use as a default would fail before the developer can configure something else. )hashlibsha1)r"rrr _lazy_sha1(sr%c@sDeZdZUdZeeZded<d ddddZdddd d d Z dS) HMACAlgorithmz*Provides signature generation using HMACs.r!default_digest_methodN) digest_methodcCs|dur|j}||_dS)N)r'r()rr(rrr__init__8szHMACAlgorithm.__init__r r cCstj|||jd}|S)N)msg digestmod)rnewr(digest)rr rmacrrrr>szHMACAlgorithm.get_signature)N) rrrr staticmethodr%r'__annotations__r)rrrrrr&0s r&7str | bytes | cabc.Iterable[str] | cabc.Iterable[bytes]z list[bytes] secret_keyrcCs&t|ttfrt|gSdd|DS)NcSsg|] }t|qSrr).0srrr Ir z#_make_keys_list..) isinstancestrr r)r3rrr_make_keys_listCs r9c@seZdZUdZeeZded<dZded<d(d d d d dddddZ e ddddZ d)d ddddZ d ddddZ d ddddZd d dd d!d"Zd dd#d$d%Zd dd#d&d'Zd S)*SigneraA signer securely signs bytes, then unsigns them to verify that the value hasn't been changed. The secret key should be a random string of ``bytes`` and should not be saved to code or version control. Different salts should be used to distinguish signing in different contexts. See :doc:`/concepts` for information about the security of the secret key and salt. :param secret_key: The secret key to sign and verify with. Can be a list of keys, oldest to newest, to support key rotation. :param salt: Extra key to combine with ``secret_key`` to distinguish signatures in different contexts. :param sep: Separator between the signature and value. :param key_derivation: How to derive the signing key from the secret key and salt. Possible values are ``concat``, ``django-concat``, or ``hmac``. Defaults to :attr:`default_key_derivation`, which defaults to ``django-concat``. :param digest_method: Hash function to use when generating the HMAC signature. Defaults to :attr:`default_digest_method`, which defaults to :func:`hashlib.sha1`. Note that the security of the hash alone doesn't apply when used intermediately in HMAC. :param algorithm: A :class:`SigningAlgorithm` instance to use instead of building a default :class:`HMACAlgorithm` with the ``digest_method``. .. versionchanged:: 2.0 Added support for key rotation by passing a list to ``secret_key``. .. versionchanged:: 0.18 ``algorithm`` was added as an argument to the class constructor. .. versionchanged:: 0.14 ``key_derivation`` and ``digest_method`` were added as arguments to the class constructor. r!r' django-concatr8default_key_derivationitsdangerous.Signer.Nr1zstr | bytes | Nonez str | bytesz str | Nonez t.Any | NonezSigningAlgorithm | None)r3saltsepkey_derivationr( algorithmcCst||_t||_|jtvr&td|dur8t|}nd}||_|durP|j}||_|durd|j }||_ |dur|t |j }||_ dS)NzThe given separator cannot be used because it may be contained in the signature itself. ASCII letters, digits, and '-_=' must not be used.r=) r9 secret_keysrr@r ValueErrorr?r<rAr'r(r&rB)rr3r?r@rAr(rBrrrr)s&     zSigner.__init__r )rcCs |jdS)zThe newest (last) entry in the :attr:`secret_keys` list. This is for compatibility from before key rotation support was added. )rC)rrrrr3szSigner.secret_keyr2cCs|dur|jd}nt|}|jdkrBtt||j|S|jdkrltt||jd|S|jdkrt j ||jd}| |j|S|jdkr|St d dS) aThis method is called to derive the key. The default key derivation choices can be overridden here. Key derivation is not intended to be used as a security method to make a complex key out of a short password. Instead you should use large random secret keys. :param secret_key: A specific secret key to derive from. Defaults to the last item in :attr:`secret_keys`. .. versionchanged:: 2.0 Added the ``secret_key`` parameter. NrEconcatr;ssignerr)r+nonezUnknown key derivation method) rCrrAtcastr r(r?r-rr,update TypeError)rr3r.rrr derive_keys       zSigner.derive_key)rrcCs&t|}|}|j||}t|S)z*Returns the signature for the given value.)rrLrBrr)rrr rrrrrszSigner.get_signaturecCst|}||j||S)zSigns the given string.)rr@r)rrrrrsignsz Signer.signr)rrrcCs^z t|}Wnty YdS0t|}t|jD]$}||}|j|||r4dSq4dS)z+Verifies the signature for the given value.FT)r ExceptionrreversedrCrLrBr)rrrr3r rrrrs   zSigner.verify_signature) signed_valuercCs^t|}|j|vr$td|jd||jd\}}|||rF|Std|d|ddS)zUnsigns the given string.zNo z found in valuerz Signature z does not match)payloadN)rr@r rsplitr)rrPrrrrrunsigns  z Signer.unsigncCs*z||WdSty$YdS0dS)znOnly validates the given signed value. Returns ``True`` if the signature exists and is valid. TFN)rSr )rrPrrrvalidates   zSigner.validate)r=r>NNN)N)rrrrr/r%r'r0r<r)propertyr3rLrrMrrSrTrrrrr:Ls" + .!r:)r ) __future__rcollections.abcabcZcabcr#rtypingrHencodingrrrrexcr r rr%r&r9r:rrrrs