Current File : //usr/lib64/python2.7/site-packages/Crypto/Cipher/PKCS1_v1_5.pyc
�
Bd\Rc@s^dZdZddgZddlmZddlTddlZdd
d��YZd	�ZdS(s[RSA encryption protocol according to PKCS#1 v1.5

See RFC3447__ or the `original RSA Labs specification`__ .

This scheme is more properly called ``RSAES-PKCS1-v1_5``.

**If you are designing a new protocol, consider using the more robust PKCS#1 OAEP.**

As an example, a sender may encrypt a message in this way:

        >>> from Crypto.Cipher import PKCS1_v1_5
        >>> from Crypto.PublicKey import RSA
        >>> from Crypto.Hash import SHA
        >>>
        >>> message = 'To be encrypted'
        >>> h = SHA.new(message)
        >>>
        >>> key = RSA.importKey(open('pubkey.der').read())
        >>> cipher = PKCS1_v1_5.new(key)
        >>> ciphertext = cipher.encrypt(message+h.digest())

At the receiver side, decryption can be done using the private part of
the RSA key:

        >>> From Crypto.Hash import SHA
        >>> from Crypto import Random
        >>>
        >>> key = RSA.importKey(open('privkey.der').read())
        >>>
        >>> dsize = SHA.digest_size
        >>> sentinel = Random.new().read(15+dsize)      # Let's assume that average data length is 15
        >>>
        >>> cipher = PKCS1_v1_5.new(key)
        >>> message = cipher.decrypt(ciphertext, sentinel)
        >>>
        >>> digest = SHA.new(message[:-dsize]).digest()
        >>> if digest==message[-dsize:]:                # Note how we DO NOT look for the sentinel
        >>>     print "Encryption was correct."
        >>> else:
        >>>     print "Encryption was not correct."

:undocumented: __revision__, __package__

.. __: http://www.ietf.org/rfc/rfc3447.txt
.. __: http://www.rsa.com/rsalabs/node.asp?id=2125.
s$Id$tnewtPKCS115_Cipheri����(tceil_div(t*NcBs;eZdZd�Zd�Zd�Zd�Zd�ZRS(sAThis cipher can perform PKCS#1 v1.5 RSA encryption or decryption.cCs
||_dS(sInitialize 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.
        N(t_key(tselftkey((s>/usr/lib64/python2.7/site-packages/Crypto/Cipher/PKCS1_v1_5.pyt__init__PscCs
|jj�S(s=Return True if this cipher object can be used for encryption.(Rtcan_encrypt(R((s>/usr/lib64/python2.7/site-packages/Crypto/Cipher/PKCS1_v1_5.pyRZscCs
|jj�S(s=Return True if this cipher object can be used for decryption.(Rtcan_decrypt(R((s>/usr/lib64/python2.7/site-packages/Crypto/Cipher/PKCS1_v1_5.pyR	^scCs�|jj}tjjj|jj�}t|d�}t|�}||dkrat	d��ndd	d��Y}t
t||�|||d���}td�|t
d�|}|jj|d�d}	t
d�|t|	�|	}
|
S(
s�Produce the PKCS#1 v1.5 encryption of a message.
    
        This function is named ``RSAES-PKCS1-V1_5-ENCRYPT``, and is specified in
        section 7.2.1 of RFC3447.
        For a complete example see `Crypto.Cipher.PKCS1_v1_5`.
    
        :Parameters:
         message : byte string
                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.
    
        :Return: A byte string, the ciphertext in which the message is encrypted.
            It is as long as the RSA modulus (in bytes).
        :Raise ValueError:
            If the RSA key length is not sufficiently long to deal with the given
            message.

        iisPlaintext is too long.tnonZeroRandBytecBseZd�Zd�ZRS(cSs
||_dS(N(trf(RR((s>/usr/lib64/python2.7/site-packages/Crypto/Cipher/PKCS1_v1_5.pyR�scSs0x)t|�dkr+|jd�d}qW|S(Nii(tbordR(Rtc((s>/usr/lib64/python2.7/site-packages/Crypto/Cipher/PKCS1_v1_5.pyt__call__�s(t__name__t
__module__RR(((s>/usr/lib64/python2.7/site-packages/Crypto/Cipher/PKCS1_v1_5.pyR
�s	iti((Rt	_randfunctCryptotUtiltnumbertsizetnRtlent
ValueErrorttobytestmaptbtbchrtencrypt(RtmessagetrandFunctmodBitstktmLenR
tpstemtmR
((s>/usr/lib64/python2.7/site-packages/Crypto/Cipher/PKCS1_v1_5.pyRbs)cCs�tjjj|jj�}t|d�}t|�|krKtd��n|jj	|�}t
d�|t|�|}|jt
d�d�}|jt
d��s�|dkr�|S||dS(s�
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 RFC3447.
        For a complete example see `Crypto.Cipher.PKCS1_v1_5`.
    
        :Parameters:
         ct : byte string
                The ciphertext that contains the message to recover.
         sentinel : any type
                The object to return to indicate that an error was detected during decryption.
    
        :Return: A byte string. It is either the original message or the ``sentinel`` (in case of an error).
        :Raise ValueError:
            If the ciphertext length is incorrect
        :Raise TypeError:
            If the RSA key has no private half.
    
        :attention:
            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^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
    
        is!Ciphertext with incorrect length.iiRi
i(RRRRRRRRRtdecryptRtfindt
startswithR(RtcttsentinelR!R"R&R%tsep((s>/usr/lib64/python2.7/site-packages/Crypto/Cipher/PKCS1_v1_5.pyR'�s7"(RRt__doc__RRR	RR'(((s>/usr/lib64/python2.7/site-packages/Crypto/Cipher/PKCS1_v1_5.pyRMs	
			.cCs
t|�S(s=Return a cipher object `PKCS115_Cipher` that can be used to perform PKCS#1 v1.5 encryption or decryption.

    :Parameters:
     key : RSA key object
      The key to use to encrypt or decrypt the message. This is a `Crypto.PublicKey.RSA` object.
      Decryption is only possible if *key* is a private RSA key.

    (R(R((s>/usr/lib64/python2.7/site-packages/Crypto/Cipher/PKCS1_v1_5.pyR�s	((	R-t__revision__t__all__tCrypto.Util.numberRtCrypto.Util.py3compatRRR(((s>/usr/lib64/python2.7/site-packages/Crypto/Cipher/PKCS1_v1_5.pyt<module>Ds
�