Mailman 3 March 2016 - Cryptography-dev

OpenSSL naming permission
by Stephen Hjerpe April 1, 2016

April 1, 2016

Hi, My understanding is that the OpenSSL license states, "Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project." Please provide some reference on the pyOpenSSL site making it clear that this permission has been obtained. Thanks, Stephen Hjerpe Development Manager stephen.hjerpe(a)microfocus.com<mailto:your.email@microfous.com> (661) 821-8917 (858) 354-8146 (mobile)

2 1

PyCA/cryptography 1.3.1 released
by Paul Kehrer March 21, 2016

March 21, 2016

PyCA/cryptography 1.3.1 was just released to PyPI. This is a minor bugfix release that fixes the following: * Fixed a bug that caused an AttributeError when using mock to patch some cryptography modules. -Paul Kehrer (reaperhulk)

1 0

accessing elliptic curve domain parameters (a/b/p/etc)
by Matt Bullock March 20, 2016

March 20, 2016

For a project I am working on, I have a need to encode/decode elliptic curve points using point compression[1]. As this is not yet supported natively by the cryptography library, I have started implementing it myself but have hit a snag. Unlike the uncompressed point encoding, in order to decode a compressed curve point I need to be able to reference the curve parameters. I have been searching through the cryptography documentation and code but cannot find any way of retrieving these values from the backend. Is there a method for this that I am missing, or is this functionality not yet available? thanks --Matt [1] 2.3.3/2.3.4 http://www.secg.org/sec1-v2.pdf

2 4

pyOpenSSL 16.0.0 released
by Hynek Schlawack March 19, 2016

March 19, 2016

On behalf of PyCA – the Python Cryptography Authority – I’m anxious to announce that after almost a year since the 0.15.1 release of pyOpenSSL we’ve released the brand new 16.0.0. A few organizational notes: 1. The pyopenssl-users mailing list and #pyopenssl IRC channel are deprecated. Please use cryptography-dev <https://mail.python.org/pipermail/cryptography-dev/> and #cryptography-dev on Freenode where you’re much more likely to get help. 2. The version scheme switched to CalVer because a 0.x version for a 15 years old project is rather odd and calling it 1.0 although we don’t expect a 2.0 to ever happen didn’t make any sense. pyOpenSSL is a long-running project with strict backward-compatibility requirements and is hence better served with a calendar-based version scheme. 3. Please note that some of us will be doing a TLS/HTTPS workshop at PyCon US 2016 so if you always wanted to learn about these things first hand, make sure to sign up: <https://us.pycon.org/2016/schedule/presentation/1786/>. We've opted to receive no compensation and asked the organizers to send them to PyLadies instead. So you’ll be doing good while learning something! *** Release details: While the list of changes looks short, a lot internal work happened: 72 files changed, 15511 insertions(+), 15063 deletions(-) We’ve done our best to not break any existing applications; including by making the urllib3 and Twisted test suites part of our CI. The full changelog can be found at <https://pyopenssl.readthedocs.org/en/stable/changelog.html>. This is the first release under full stewardship of PyCA. We have made many changes to make local development more pleasing. The test suite now passes both on Linux and OS X with OpenSSL 0.9.8, 1.0.1, and 1.0.2. It has been moved to py.test, all CI test runs are part of tox and the source code has been made fully flake8 compliant. We hope to have lowered the barrier for contributions significantly but are open to hear about any remaining frustrations. Backward-incompatible changes: • Python 3.2 support has been dropped. It never had significant real world usage and has been dropped by our main dependency cryptography. Affected users should upgrade to Python 3.3 or later. Deprecations: • The support for EGD has been removed. The only affected function OpenSSL.rand.egd() now uses os.urandom() to seed the internal PRNG instead. Please see pyca/cryptography#1636 for more background information on this decision. In accordance with our backward compatibility policy OpenSSL.rand.egd() will be removed no sooner than a year from the release of 16.0.0. Please note that you should use urandom for all your secure random number needs. • Python 2.6 support has been deprecated. Our main dependency cryptography deprecated 2.6 in version 0.9 (2015-05-14) with no time table for actually dropping it. pyOpenSSL will drop Python 2.6 support once cryptography does. Changes: • Fixed OpenSSL.SSL.Context.set_session_id, OpenSSL.SSL.Connection.renegotiate, OpenSSL.SSL.Connection.renegotiate_pending, and OpenSSL.SSL.Context.load_client_ca. They were lacking an implementation since 0.14. #422 • Fixed segmentation fault when using keys larger than 4096-bit to sign data. #428 • Fixed AttributeError when OpenSSL.SSL.Connection.get_app_data() was called before setting any app data. #304 • Added OpenSSL.crypto.dump_publickey() to dump OpenSSL.crypto.PKey objects that represent public keys, and OpenSSL.crypto.load_publickey() to load such objects from serialized representations. #382 • Added OpenSSL.crypto.dump_crl() to dump a certificate revocation list out to a string buffer. #368 • Added OpenSSL.SSL.Connection.get_state_string() using the OpenSSL binding state_string_long. #358 • Added support for the socket.MSG_PEEK flag to OpenSSL.SSL.Connection.recv() and OpenSSL.SSL.Connection.recv_into(). #294 • Added OpenSSL.SSL.Connection.get_protocol_version() and OpenSSL.SSL.Connection.get_protocol_version_name(). #244 • Switched to utf8string mask by default. OpenSSL formerly defaulted to a T61String if there were UTF-8 characters present. This was changed to default to UTF8String in the config around 2005, but the actual code didn't change it until late last year. This will default us to the setting that actually works. To revert this you can call OpenSSL.crypto._lib.ASN1_STRING_set_default_mask_asc(b"default"). #234 *** For PyCA, Hynek Schlawack

1 0

PyCA/cryptography 1.3 released
by Paul Kehrer March 18, 2016

March 18, 2016

On behalf of all our contributors I am pleased to announce the release of PyCA/cryptography (https://github.com/pyca/cryptography) version 1.3. cryptography is a package which provides cryptographic recipes and primitives to Python developers. Our goal is for it to be your "cryptographic standard library". We support Python 2.6-2.7, Python 3.3+, and PyPy. Changelog (https://cryptography.io/en/latest/changelog/): * Added support for padding ANSI X.923 with ANSIX923. * Deprecated support for OpenSSL 0.9.8. Support will be removed in cryptography 1.4. * Added support for the PolicyConstraints X.509 extension including both parsing and generation using CertificateBuilder and CertificateSigningRequestBuilder. * Added is_signature_valid to CertificateSigningRequest. * Fixed an intermittent AssertionError when performing an RSA decryption on an invalid ciphertext, ValueError is now correctly raised in all cases. * Added from_issuer_subject_key_identifier(). ...and the typical miscellaneous improvements. Please see the website changelog for documentation and additional details. -Paul Kehrer (reaperhulk)

1 0

Upcoming pyOpenSSL release
by Hynek Schlawack March 17, 2016

March 17, 2016

Hi, after a (too) long time, we’re zeroing in to a new pyOpenSSL release. Currently we’re mostly waiting for cryptography 1.3 to drop and to understand this very scary test failure: https://github.com/pyca/pyopenssl/issues/447 *** At that occasion, I would like to raise a few questions and explanations: # The version number will now follow CalVer. It’s known that I don’t like SemVer, however this case is a bit more subtle. pyOpenSSL is old and mature. Therefore a 0.x version is ludicrous. However going 1.0 doesn’t make any sense because there will never be a 2.0. We will keep it alive as long as possible, but there will be no compatibility breaking changes to be expected. I still believe in cryptography.tls. # The communities need to coalesce. This is both an announcement and a question. I refuse to take care of the #pyopenssl channel and the pyopenssl-users mailing list. They have to be merged into PyCa. Now the question is: should I just send everyone to cryptography-dev and #cryptography-dev or are we going forth and finally do a #pyca/#pyca-dev channels and/or mailing lists? # Domain? We spoke a few times about it without a real conclusion. I find having a pyca.io like pypa.io would be neato. # CoC The PSF CoC is crap. Anyone opposed adopting http://contributor-covenant.org which seems to be the general consensus outside “my constitutional rights are violated if I can’t go full Torvalds in code review” circles? Best, —h

5 5

PyCA cryptography 1.2.3 released
by Paul Kehrer March 2, 2016

March 2, 2016

PyCA cryptography 1.2.3 has been released to PyPI. This version updates the Windows and OS X wheels to be compiled with OpenSSL 1.0.2g. -Paul Kehrer (reaperhulk)

1 0