Файловый менеджер - Редактировать - /opt/imh-python/lib/python3.9/site-packages/Cryptodome/Cipher/__pycache__/PKCS1_v1_5.cpython-39.pyc
Ðазад
a c�h+ � @ s\ d dgZ ddlmZmZmZ ddlmZmZ ddlZddlm Z G dd� d�Z d dd �Z dS ) �new�PKCS115_Cipher� )�ceil_div� bytes_to_long� long_to_bytes)�bord� _copy_bytesN)�Randomc @ s8 e Zd ZdZdd� Zdd� Zdd� Zdd � Zd d � Zd S ) r z�This cipher can perform PKCS#1 v1.5 RSA encryption or decryption. Do not instantiate directly. Use :func:`Cryptodome.Cipher.PKCS1_v1_5.new` instead.c C s || _ || _dS )aJ Initialize this PKCS#1 v1.5 cipher object. :Parameters: key : an RSA key object If a private half is given, both encryption and decryption are possible. If a public half is given, only encryption is possible. randfunc : callable Function that returns random bytes. N)�_key� _randfunc)�self�key�randfunc� r ��/root/rpmbuild/BUILDROOT/imh-python39-modules-3.9.7-92.el8.x86_64/opt/imh-python/lib/python3.9/site-packages/Cryptodome/Cipher/PKCS1_v1_5.py�__init__" s zPKCS115_Cipher.__init__c C s | j �� S )z=Return True if this cipher object can be used for encryption.)r � can_encrypt�r r r r r 0 s zPKCS115_Cipher.can_encryptc C s | j �� S )z=Return True if this cipher object can be used for decryption.)r � can_decryptr r r r r 4 s zPKCS115_Cipher.can_decryptc C s� t jj�| jj�}t|d�}t|�}||d kr8td��g }t|�|| d krx| � d�}t |d �dkrlq<|� |� q<d� |�}t|�|| d ks�J �d| d t d d |� }t|�}| j�|�} t| |�} | S ) a� Produce the PKCS#1 v1.5 encryption of a message. This function is named ``RSAES-PKCS1-V1_5-ENCRYPT``, and it is specified in `section 7.2.1 of RFC8017 <https://tools.ietf.org/html/rfc8017#page-28>`_. :param message: The message to encrypt, also known as plaintext. It can be of variable length, but not longer than the RSA modulus (in bytes) minus 11. :type message: bytes/bytearray/memoryview :Returns: A byte string, the ciphertext in which the message is encrypted. It is as long as the RSA modulus (in bytes). :Raises ValueError: If the RSA key length is not sufficiently long to deal with the given message. � � zPlaintext is too long.� � r � � � N)� Cryptodome�Util�number�sizer �nr �len� ValueErrorr r �append�joinr r Z_encryptr ) r �message�modBits�kZmLenZpsZnew_byte�emZem_int�m_int�cr r r �encrypt8 s$ zPKCS115_Cipher.encryptc C s� t jj�| jj�}t|d�}t|�|kr0td��t |�}| j� |�}t ||�}|� dd�}|� d�rl|dk rp|S ||d d� S ) a� Decrypt a PKCS#1 v1.5 ciphertext. This function is named ``RSAES-PKCS1-V1_5-DECRYPT``, and is specified in `section 7.2.2 of RFC8017 <https://tools.ietf.org/html/rfc8017#page-29>`_. :param ciphertext: The ciphertext that contains the message to recover. :type ciphertext: bytes/bytearray/memoryview :param sentinel: The object to return whenever an error is detected. :type sentinel: any type :Returns: A byte string. It is either the original message or the ``sentinel`` (in case of an error). :Raises ValueError: If the ciphertext length is incorrect :Raises TypeError: If the RSA key has no private half (i.e. it cannot be used for decyption). .. warning:: You should **never** let the party who submitted the ciphertext know that this function returned the ``sentinel`` value. Armed with such knowledge (for a fair amount of carefully crafted but invalid ciphertexts), an attacker is able to recontruct the plaintext of any other encryption that were carried out with the same RSA public key (see `Bleichenbacher's`__ attack). In general, it should not be possible for the other party to distinguish whether processing at the server side failed because the value returned was a ``sentinel`` as opposed to a random, invalid message. In fact, the second option is not that unlikely: encryption done according to PKCS#1 v1.5 embeds no good integrity check. There is roughly one chance in 2\ :sup:`16` for a random ciphertext to be returned as a valid message (although random looking). It is therefore advisabled to: 1. Select as ``sentinel`` a value that resembles a plausable random, invalid message. 2. Not report back an error as soon as you detect a ``sentinel`` value. Put differently, you should not explicitly check if the returned value is the ``sentinel`` or not. 3. Cover all possible errors with a single, generic error indicator. 4. Embed into the definition of ``message`` (at the protocol level) a digest (e.g. ``SHA-1``). It is recommended for it to be the rightmost part ``message``. 5. Where possible, monitor the number of errors due to ciphertexts originating from the same party, and slow down the rate of the requests from such party (or even blacklist it altogether). **If you are designing a new protocol, consider using the more robust PKCS#1 OAEP.** .. __: http://www.bell-labs.com/user/bleichen/papers/pkcs.ps r z!Ciphertext with incorrect length.r � r � r N)r r r r r r r r! r" r Z_decryptr �find� startswith) r Z ciphertext�sentinelr& r' Zct_intr) r( �sepr r r �decryptg s 9 zPKCS115_Cipher.decryptN) �__name__� __module__� __qualname__�__doc__r r r r+ r2 r r r r r s /c C s |du rt j}t| |�S )a� Create a cipher for performing PKCS#1 v1.5 encryption or decryption. :param key: The key to use to encrypt or decrypt the message. This is a `Cryptodome.PublicKey.RSA` object. Decryption is only possible if *key* is a private RSA key. :type key: RSA key object :param randfunc: Function that return random bytes. The default is :func:`Cryptodome.Random.get_random_bytes`. :type randfunc: callable :returns: A cipher object `PKCS115_Cipher`. N)r Zget_random_bytesr )r r r r r r � s )N) �__all__ZCryptodome.Util.numberr r r ZCryptodome.Util.py3compatr r r r r r r r r r �<module> s
| ver. 1.1 | |
.
| PHP 8.3.30 | Ð“ÐµÐ½ÐµÑ€Ð°Ñ†Ð¸Ñ Ñтраницы: 0 |
proxy
|
phpinfo
|
ÐаÑтройка