Changelog for python3-pycrypto-2.6.1-lp152.6.6.x86_64.rpm :

* Wed Apr 01 2020 John Vandenberg - Support Python 3.8 by adapting use-time-process-time.patch from https://github.com/dlitz/pycrypto/pull/296
* Fri May 05 2017 toddrme2178AATTgmail.com- There was never a python3-crypto so don\'t provide it.
* Mon May 01 2017 toddrme2178AATTgmail.com- Implement single-spec version.- Use Pypi source URL.
* Wed Jan 04 2017 vuntzAATTsuse.com- Add CVE-2013-7459.patch: python-pycrypto: Heap buffer overflow in ALGnew (bsc#1017420).
* Wed Apr 23 2014 rschweikertAATTsuse.com- Include in SLE 12 (FATE #315990)
* Wed Nov 27 2013 p.drouandAATTgmail.com- Update to version 2.6.1
* [CVE-2013-1445] Fix PRNG not correctly reseeded in some situations. In previous versions of PyCrypto, the Crypto.Random PRNG exhibits a race condition that may cause forked processes to generate identical sequences of \'random\' numbers. This is a fairly obscure bug that will (hopefully) not affect many applications, but the failure scenario is pretty bad. Here is some sample code that illustrates the problem: from binascii import hexlify import multiprocessing, pprint, time import Crypto.Random def task_main(arg): a = Crypto.Random.get_random_bytes(8) time.sleep(0.1) b = Crypto.Random.get_random_bytes(8) rdy, ack = arg rdy.set() ack.wait() return \"%s,%s\" % (hexlify(a).decode(), hexlify(b).decode()) n_procs = 4 manager = multiprocessing.Manager() rdys = [manager.Event() for i in range(n_procs)] acks = [manager.Event() for i in range(n_procs)] Crypto.Random.get_random_bytes(1) pool = multiprocessing.Pool(processes=n_procs, initializer=Crypto.Random.atfork) res_async = pool.map_async(task_main, zip(rdys, acks)) pool.close() [rdy.wait() for rdy in rdys] [ack.set() for ack in acks] res = res_async.get() pprint.pprint(sorted(res)) pool.join() The output should be random, but it looked like this: [\'c607803ae01aa8c0,2e4de6457a304b34\', \'c607803ae01aa8c0,af80d08942b4c987\', \'c607803ae01aa8c0,b0e4c0853de927c4\', \'c607803ae01aa8c0,f0362585b3fceba4\'] This release fixes the problem by resetting the rate-limiter when Crypto.Random.atfork() is invoked. It also adds some tests and a few related comments.- Add \"-fno-strict-aliasing\" to CFLAGS
* Wed Jun 12 2013 dmuellerAATTsuse.com- add ignore-fastmath-warning.diff for SLE11 and older
* Wed Apr 24 2013 highwaystar.ruAATTgmail.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)
* Mon Sep 03 2012 jengelhAATTinai.de- Make package build on RH6-like systems
* Thu May 24 2012 highwaystar.ruAATTgmail.com- python3 package added- minor spec improvement