Mailman 3 March 2014 - Cryptography-dev

cryptography 0.3
by Paul Kehrer March 28, 2014

March 28, 2014

The third major release of cryptography is now released. A huge thank you to all the contributors who submitted PRs, reviewed code, and helped with API design. The major highlights of this release can be found in our changelog (https://cryptography.io/en/latest/changelog/) but we also expanded our OpenSSL support to handle RHEL5, dramatically expanded our test infrastructure (FreeBSD, OpenSSL 1.0.2beta1, RHEL5, Python 3.4), put in some changes around cffi releases, added additional OpenSSL bindings, and many other improvements. -Paul

2 2

Cryptography Third Release (0.3) Criteria
by Paul Kehrer March 15, 2014

March 15, 2014

We released 0.2 on Feb 20. Since that time we’ve expanded our support for older OpenSSLs (RHEL 5 users are now supported), landed most of RSA signing and verification, further expanded the bindings for OpenSSL, added HOTP/TOTP support, and improved our error stack handling in the OpenSSL backend. I’d like to propose that we get a release out in the next week or two that has the following features (in addition to the above): * Fix for our windows wheels breaking when cffi does a minor release (https://github.com/pyca/cryptography/pull/768) * Completion of RSA PSS (MGF1 PR here: https://github.com/pyca/cryptography/pull/775, two more upcoming PRs are dependent on this to finish out PSS) * OpenSSL (“PKCS1”) key loading/writing. (loader PR: https://github.com/pyca/cryptography/pull/627) * Using hex()/from_bytes for BN conversions in the OpenSSL backend (https://github.com/pyca/cryptography/pull/759) * Split the test vectors out of the primary sdist and put them in a separate package. (https://github.com/pyca/cryptography/pull/795). Is there anything else people feel should be present in the 0.3 release? DSA support might make it in, but there’s enough work left there that I believe it’s a better candidate for the fourth release. I’ll go ahead and volunteer as release manager for this release as well. I’m going to go ahead and add a fourth release milestone and begin retargeting some of our issues. -Paul

2 1

Ancient OpenSSL Support
by Paul Kehrer March 11, 2014

March 11, 2014

A user filed an issue today asking us to support 0.9.8b (https://github.com/pyca/cryptography/issues/727#issuecomment-37133554), which shipped in Fedora 8 (apparently used by http://www.planet-lab.org). The patch is actually very small, but we don’t have CI coverage for any distribution using OpenSSL that ancient (Fedora 8 was released 7 years ago and has been out of support for over 5). I’m also concerned that this sets a precedent where we’ll have difficulty *ever* removing support for an OpenSSL version (and the 0.9.8e patches would be very nice to remove in a few years). So, what do we want to do here? I’m -1 on landing it and claiming it as an officially supported version, but -0.5 on landing it with no guarantees of future functionality since we’re not testing against it. On a related note, we should probably document our official minimum OpenSSL version somewhere in the docs (currently 0.9.8e). -Paul

4 4

Building on Windows 7, 64x
by kab March 9, 2014

March 9, 2014

Congratulations on the release Given the nature of the package, I opted to build everything from source. I started with openssl-1.0.0l and once that was built and installed, I set the include and lib environment variables for cryptography's build process to use. It turns out, however, that the openssl build creates two libraries: libeay32.lib and ssleay32.lib. This of course cause the build process of cryptography to fail since it cannot find crypto.lib and ssl.lib. But since I've come to know that libeay32.lib is crypto.lib and likewise ssleay32.lib is ssl.lib, I copied the original libraries (libeay32.lib and ssleay32.lib) to the same directory they were installed in by the openssl installation process and renamed them crypto.lib and ssl.lib respectively. This made cryptography's build complete successfully and the package was installed without problems. Here is the summary output of py.test: =================================== ERRORS ==================================== ____________________ ERROR collecting tests/test_fernet.py ____________________ tests\test_fernet.py:40: in <module> > class TestFernet(object): tests\test_fernet.py:42: in TestFernet > ("secret", "now", "iv", "src", "token"), "generate.json", tests\test_fernet.py:32: in json_parametrize > with open(path) as f: E IOError: [Errno 2] No such file or directory: 'J:\\projs\\cryptograp hy-0.1\\tests\\vectors\\fernet\\generate.json' =========== 15473 passed, 47261 skipped, 1 error in 291.69 seconds ============ I hope someone will find this useful. Khalid

1 0

Latest release does not build on Windows
by Khalid [KAB] March 4, 2014

March 4, 2014

I want to report that unlike the 0.1 release, the latest cryptography release-- namely 0.2.1-- does not build on Windows. Building from the repository now succeeds however. For reference, this was tested after commit 930eed8bcbea6f6250998f0ee042babd62667a9f. Regards, Khalid

2 5

cryptography 0.2.2 Released
by Paul Kehrer March 4, 2014

March 4, 2014

0.2.2 has been released to resolve an issue where compilation could fail if an error code (EVP_R_DISABLED_FOR_FIPS) was not present in the user’s OpenSSL installation. -Paul Kehrer

1 0