Why Gemfury? Push, build, and install  RubyGems npm packages Python packages Maven artifacts PHP packages Go Modules Debian packages RPM packages NuGet packages

Repository URL to install this package:

Details    
pycryptodomex / Doc / src / vs_pycrypto.rst
Size: Mime:
Compatibility with PyCrypto
===========================

PyCryptodome exposes *almost* the same API as the old `PyCrypto <https://www.dlitz.net/software/pycrypto>`_
so that *most* applications will run unmodified.
However, a very few breaks in compatibility had to be introduced
for those parts of the API that represented a security hazard or that
were too hard to maintain.

Specifically, for public key cryptography:

* The following methods from public key objects (RSA, DSA, ElGamal) have been
  removed:
  
  - :meth:`sign`
  - :meth:`verify`
  - :meth:`encrypt`
  - :meth:`decrypt`
  - :meth:`blind`
  - :meth:`unblind`

  Applications should be updated to use instead:

  - :mod:`Crypto.Cipher.PKCS1_OAEP` for encrypting using RSA.
  - :mod:`Crypto.Signature.pkcs1_15` or :mod:`Crypto.Signature.pss` for signing using RSA.
  - :mod:`Crypto.Signature.DSS` for signing using DSA.
* Method: :meth:`generate` for public key modules does not accept the ``progress_func`` parameter anymore.
* Ambiguous method ``size`` from RSA, DSA and ElGamal key objects have been removed.
  Instead, use methods :meth:`size_in_bytes` and :meth:`size_in_bits` and check the documentation.
* The 3 public key object types (RSA, DSA, ElGamal) are now unpickable.
  You must use the :meth:`export_key` method of each key object and select a good output format: for private
  keys that means a good password-based encryption scheme.
* Removed attribute ``Crypto.PublicKey.RSA.algorithmIdentifier``.
* Removed ``Crypto.PublicKey.RSA.RSAImplementation`` (which should have been private in the first place).
  Same for ``Crypto.PublicKey.DSA.DSAImplementation``.

For symmetric key cryptography:

* Symmetric ciphers do not have ECB as default mode anymore. ECB is not semantically secure
  and it exposes correlation across blocks.
  An expression like ``AES.new(key)`` will now fail. If ECB is the desired mode,
  one has to explicitly use ``AES.new(key, AES.MODE_ECB)``.
* :mod:`Crypto.Cipher.DES3` does not allow keys that degenerate to Single DES.
* Parameter :data:`segment_size` cannot be 0 for the CFB mode.
* Parameters ``disabled_shortcut`` and ``overflow`` cannot be passed anymore to :mod:`Crypto.Util.Counter.new`.
  Parameter :data:`allow_wraparound` is ignored (counter block wraparound will **always** be checked).
* The :data:`counter` parameter of a CTR mode cipher must be generated via
  :mod:`Crypto.Util.Counter`. It cannot be a generic callable anymore.
* Keys for :mod:`Crypto.Cipher.ARC2`, :mod:`Crypto.Cipher.ARC4` and :mod:`Crypto.Cipher.Blowfish` must be at least 40 bits long (still very weak).

The following packages, modules and functions have been removed:

    - ``Crypto.Random.OSRNG``, ``Crypto.Util.winrandom`` and ``Crypto.Random.randpool``.
      You should use :mod:`Crypto.Random` only.
    - ``Crypto.Cipher.XOR``. If you just want to XOR data, use :mod:`Crypto.Util.strxor`.
    - ``Crypto.Hash.new``. Use :func:`Crypto.Hash.<algorithm>.new` instead.
    - ``Crypto.Protocol.AllOrNothing``
    - ``Crypto.Protocol.Chaffing``
    - ``Crypto.Util.number.getRandomNumber``
    - ``Crypto.pct_warnings``

Others:

* Support for any Python version older than 2.6 is dropped.