File python3-pycrypto.changes of Package python3-pycrypto

Overview Repositories Revisions Requests Users Attributes Meta

File python3-pycrypto.changes of Package python3-pycrypto (Revision b59d57e82d6a8b7b0d1b716cde4132bc)

Currently displaying revision b59d57e82d6a8b7b0d1b716cde4132bc , Show latest

-------------------------------------------------------------------
Sun May  8 07:04:42 UTC 2016 - arun@gmx.de

- specfile:
  * changed to https for source url
  * updated source url to files.pythonhosted.org

-------------------------------------------------------------------
Wed Oct 21 11:36:58 UTC 2015 - toddrme2178@gmail.com

- Don't build with python3-buildservice-tweak.
  The package detects the lack of randomness and aborts the build.

-------------------------------------------------------------------
Sun Dec 21 23:47:47 UTC 2014 - p.drouand@gmail.com

- Remove useless make requirements
- Remove repreciated python(abi) rependency
- Remove unapplied ignore-fastmath-warning.diff

-------------------------------------------------------------------
Thu Dec 18 18:30:25 UTC 2014 - arun@gmx.de

- update to version 2.6.1:
  * [CVE-2013-1445] Fix PRNG not correctly reseeded in some situations.

-------------------------------------------------------------------
Wed Apr 24 06:55:47 UTC 2013 - highwaystar.ru@gmail.com

- update to 2.6 
  * [CVE-2012-2417] Fix LP#985164: insecure ElGamal key generation.
    (thanks: Legrandin)

In the ElGamal schemes (for both encryption and signatures), g is
    supposed to be the generator of the entire Z^*_p group.  However, in
    PyCrypto 2.5 and earlier, g is more simply the generator of a random
    sub-group of Z^*_p.

The result is that the signature space (when the key is used for
    signing) or the public key space (when the key is used for encryption)
    may be greatly reduced from its expected size of log(p) bits, possibly
    down to 1 bit (the worst case if the order of g is 2).

While it has not been confirmed, it has also been suggested that an
    attacker might be able to use this fact to determine the private key.

Anyone using ElGamal keys should generate new keys as soon as practical.

Any additional information about this bug will be tracked at
    https://bugs.launchpad.net/pycrypto/+bug/985164

* Huge documentation cleanup (thanks: Legrandin).

* Added more tests, including test vectors from NIST 800-38A
    (thanks: Legrandin)

* Remove broken MODE_PGP, which never actually worked properly.
    A new mode, MODE_OPENPGP, has been added for people wishing to write
    OpenPGP implementations.  Note that this does not implement the full
    OpenPGP specification, only the "OpenPGP CFB mode" part of that
    specification.
    https://bugs.launchpad.net/pycrypto/+bug/996814

* Fix: getPrime with invalid input causes Python to abort with fatal error
    https://bugs.launchpad.net/pycrypto/+bug/988431

* Fix: Segfaults within error-handling paths
    (thanks: Paul Howarth & Dave Malcolm)
    https://bugs.launchpad.net/pycrypto/+bug/934294

* Fix: Block ciphers allow empty string as IV
    https://bugs.launchpad.net/pycrypto/+bug/997464

* Fix DevURandomRNG to work with Python3's new I/O stack.
    (thanks: Sebastian Ramacher)

* Remove automagic dependencies on libgmp and libmpir, let the caller
    disable them using args.

* Many other minor bug fixes and improvements (mostly thanks to Legrandin)

-------------------------------------------------------------------
Thu Nov 22 13:47:34 UTC 2012 - toddrme2178@gmail.com

- Removed openSUSE 11.4 spec file workarounds

-------------------------------------------------------------------
Thu May 24 03:07:52 UTC 2012 - highwaystar.ru@gmail.com

- python3-pycrypto package added

Places

File python3-pycrypto.changes of Package python3-pycrypto (Revision b59d57e82d6a8b7b0d1b716cde4132bc)

Places