From khabkr at yahoo.com Mon Mar 3 18:21:37 2014 From: khabkr at yahoo.com (Khalid [KAB]) Date: Mon, 03 Mar 2014 19:21:37 +0200 Subject: [Cryptography-dev] Latest release does not build on Windows Message-ID: <5314BA21.5020401@yahoo.com> 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 From paul.l.kehrer at gmail.com Mon Mar 3 18:28:18 2014 From: paul.l.kehrer at gmail.com (Paul Kehrer) Date: Mon, 3 Mar 2014 13:28:18 -0400 Subject: [Cryptography-dev] Latest release does not build on Windows In-Reply-To: <5314BA21.5020401@yahoo.com> References: <5314BA21.5020401@yahoo.com> Message-ID: Could you provide the specific error you?re seeing on 0.2.1 as well as whether you?re 32 or 64-bit? Our CI infrastructure built wheels successfully for the 0.2.1 release. On Monday, March 3, 2014 at 1:21 PM, Khalid [KAB] wrote: > 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 > > > _______________________________________________ > Cryptography-dev mailing list > Cryptography-dev at python.org (mailto:Cryptography-dev at python.org) > https://mail.python.org/mailman/listinfo/cryptography-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From khabkr at yahoo.com Mon Mar 3 18:50:31 2014 From: khabkr at yahoo.com (Khalid [KAB]) Date: Mon, 03 Mar 2014 19:50:31 +0200 Subject: [Cryptography-dev] Latest release does not build on Windows In-Reply-To: References: <5314BA21.5020401@yahoo.com> Message-ID: <5314C0E7.4020108@yahoo.com> I am on Windows 7 x64 using Python 2.7.6 x64: J:\projs\cryptography-0.2.1>python Python 2.7.6 (default, Nov 10 2013, 19:24:24) [MSC v.1500 64 bit (AMD64)] on win 32 Type "help", "copyright", "credits" or "license" for more information. >>> Here is the build attempt: ------------------------------------------------------------- J:\projs\cryptography-0.2.1>set LIB=F:\dev\openssl\lib; J:\projs\cryptography-0.2.1>set INCLUDE=F:\dev\openssl\include; J:\projs\cryptography-0.2.1>python setup.py build running build running build_ext building '_cffi__xcfd0a060xfba2f231' extension creating J:\projs\cryptography-0.2.1\cryptography\hazmat\primitives\__pycache__\ Release creating J:\projs\cryptography-0.2.1\cryptography\hazmat\primitives\__pycache__\ Release\cryptography creating J:\projs\cryptography-0.2.1\cryptography\hazmat\primitives\__pycache__\ Release\cryptography\hazmat creating J:\projs\cryptography-0.2.1\cryptography\hazmat\primitives\__pycache__\ Release\cryptography\hazmat\primitives creating J:\projs\cryptography-0.2.1\cryptography\hazmat\primitives\__pycache__\ Release\cryptography\hazmat\primitives\__pycache__ f:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\amd64\cl.exe /c /nolog o /Ox /MD /W3 /GS- /DNDEBUG -IF:\Python27\include -IF:\Python27\PC /Tccryptograp hy\hazmat\primitives\__pycache__\_cffi__xcfd0a060xfba2f231.c /FoJ:\projs\cryptog raphy-0.2.1\cryptography\hazmat\primitives\__pycache__\Release\cryptography\hazm at\primitives\__pycache__\_cffi__xcfd0a060xfba2f231.obj _cffi__xcfd0a060xfba2f231.c f:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\amd64\link.exe /DLL /n ologo /INCREMENTAL:NO /LIBPATH:F:\Python27\libs /LIBPATH:F:\Python27\PCbuild\amd 64 /EXPORT:init_cffi__xcfd0a060xfba2f231 J:\projs\cryptography-0.2.1\cryptograph y\hazmat\primitives\__pycache__\Release\cryptography\hazmat\primitives\__pycache __\_cffi__xcfd0a060xfba2f231.obj /OUT:J:\projs\cryptography-0.2.1\cryptography\h azmat\primitives\__pycache__\_cffi__xcfd0a060xfba2f231.pyd /IMPLIB:J:\projs\cryp tography-0.2.1\cryptography\hazmat\primitives\__pycache__\Release\cryptography\h azmat\primitives\__pycache__\_cffi__xcfd0a060xfba2f231.lib /MANIFESTFILE:J:\proj s\cryptography-0.2.1\cryptography\hazmat\primitives\__pycache__\Release\cryptogr aphy\hazmat\primitives\__pycache__\_cffi__xcfd0a060xfba2f231.pyd.manifest _cffi__xcfd0a060xfba2f231.obj : warning LNK4197: export 'init_cffi__xcfd0a060xfb a2f231' specified multiple times; using first specification Creating library J:\projs\cryptography-0.2.1\cryptography\hazmat\primitives\_ _pycache__\Release\cryptography\hazmat\primitives\__pycache__\_cffi__xcfd0a060xf ba2f231.lib and object J:\projs\cryptography-0.2.1\cryptography\hazmat\primitive s\__pycache__\Release\cryptography\hazmat\primitives\__pycache__\_cffi__xcfd0a06 0xfba2f231.exp running build_ext building '_cffi__x5fea2bacx4a8b9ec1' extension f:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\amd64\cl.exe /c /nolog o /Ox /MD /W3 /GS- /DNDEBUG -IF:\Python27\include -IF:\Python27\PC /Tccryptograp hy\hazmat\primitives\__pycache__\_cffi__x5fea2bacx4a8b9ec1.c /FoJ:\projs\cryptog raphy-0.2.1\cryptography\hazmat\primitives\__pycache__\Release\cryptography\hazm at\primitives\__pycache__\_cffi__x5fea2bacx4a8b9ec1.obj _cffi__x5fea2bacx4a8b9ec1.c cryptography\hazmat\primitives\__pycache__\_cffi__x5fea2bacx4a8b9ec1.c(218) : wa rning C4244: '=' : conversion from 'unsigned __int64' to 'uint8_t', possible los s of data f:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\amd64\link.exe /DLL /n ologo /INCREMENTAL:NO /LIBPATH:F:\Python27\libs /LIBPATH:F:\Python27\PCbuild\amd 64 /EXPORT:init_cffi__x5fea2bacx4a8b9ec1 J:\projs\cryptography-0.2.1\cryptograph y\hazmat\primitives\__pycache__\Release\cryptography\hazmat\primitives\__pycache __\_cffi__x5fea2bacx4a8b9ec1.obj /OUT:J:\projs\cryptography-0.2.1\cryptography\h azmat\primitives\__pycache__\_cffi__x5fea2bacx4a8b9ec1.pyd /IMPLIB:J:\projs\cryp tography-0.2.1\cryptography\hazmat\primitives\__pycache__\Release\cryptography\h azmat\primitives\__pycache__\_cffi__x5fea2bacx4a8b9ec1.lib /MANIFESTFILE:J:\proj s\cryptography-0.2.1\cryptography\hazmat\primitives\__pycache__\Release\cryptogr aphy\hazmat\primitives\__pycache__\_cffi__x5fea2bacx4a8b9ec1.pyd.manifest _cffi__x5fea2bacx4a8b9ec1.obj : warning LNK4197: export 'init_cffi__x5fea2bacx4a 8b9ec1' specified multiple times; using first specification Creating library J:\projs\cryptography-0.2.1\cryptography\hazmat\primitives\_ _pycache__\Release\cryptography\hazmat\primitives\__pycache__\_cffi__x5fea2bacx4 a8b9ec1.lib and object J:\projs\cryptography-0.2.1\cryptography\hazmat\primitive s\__pycache__\Release\cryptography\hazmat\primitives\__pycache__\_cffi__x5fea2ba cx4a8b9ec1.exp running build_ext building '_cffi__xd7f460e7x5223a62c' extension creating J:\projs\cryptography-0.2.1\cryptography\hazmat\bindings\__pycache__\Re lease creating J:\projs\cryptography-0.2.1\cryptography\hazmat\bindings\__pycache__\Re lease\cryptography creating J:\projs\cryptography-0.2.1\cryptography\hazmat\bindings\__pycache__\Re lease\cryptography\hazmat creating J:\projs\cryptography-0.2.1\cryptography\hazmat\bindings\__pycache__\Re lease\cryptography\hazmat\bindings creating J:\projs\cryptography-0.2.1\cryptography\hazmat\bindings\__pycache__\Re lease\cryptography\hazmat\bindings\__pycache__ f:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\amd64\cl.exe /c /nolog o /Ox /MD /W3 /GS- /DNDEBUG -IF:\Python27\include -IF:\Python27\PC /Tccryptograp hy\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c /FoJ:\projs\cryptogra phy-0.2.1\cryptography\hazmat\bindings\__pycache__\Release\cryptography\hazmat\b indings\__pycache__\_cffi__xd7f460e7x5223a62c.obj _cffi__xd7f460e7x5223a62c.c cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(1535) : war ning C4048: different array subscripts : 'unsigned char (*)[]' and 'unsigned cha r (*)[32]' cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(1536) : war ning C4048: different array subscripts : 'unsigned char (*)[]' and 'unsigned cha r (*)[32]' cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(1560) : war ning C4048: different array subscripts : 'unsigned char (*)[]' and 'unsigned cha r (*)[48]' cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4410) : war ning C4308: negative integral constant converted to unsigned type cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4429) : war ning C4308: negative integral constant converted to unsigned type cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4448) : war ning C4308: negative integral constant converted to unsigned type cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4467) : war ning C4308: negative integral constant converted to unsigned type cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4486) : war ning C4308: negative integral constant converted to unsigned type cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4505) : war ning C4308: negative integral constant converted to unsigned type cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4524) : war ning C4308: negative integral constant converted to unsigned type cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4543) : war ning C4308: negative integral constant converted to unsigned type cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4562) : war ning C4308: negative integral constant converted to unsigned type cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4581) : war ning C4308: negative integral constant converted to unsigned type cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(5702) : err or C2065: 'EVP_R_DISABLED_FOR_FIPS' : undeclared identifier cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(5702) : err or C2065: 'EVP_R_DISABLED_FOR_FIPS' : undeclared identifier cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(5703) : err or C2065: 'EVP_R_DISABLED_FOR_FIPS' : undeclared identifier cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(5704) : err or C2065: 'EVP_R_DISABLED_FOR_FIPS' : undeclared identifier cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(5705) : err or C2065: 'EVP_R_DISABLED_FOR_FIPS' : undeclared identifier cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(5707) : err or C2065: 'EVP_R_DISABLED_FOR_FIPS' : undeclared identifier cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(8473) : war ning C4308: negative integral constant converted to unsigned type cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(11004) : wa rning C4267: 'function' : conversion from 'size_t' to 'long', possible loss of d ata cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(11004) : wa rning C4267: 'function' : conversion from 'size_t' to 'unsigned long', possible loss of data cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(11031) : wa rning C4267: 'function' : conversion from 'size_t' to 'long', possible loss of d ata cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(11031) : wa rning C4267: 'function' : conversion from 'size_t' to 'unsigned long', possible loss of data cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(13630) : wa rning C4244: 'function' : conversion from 'uintptr_t' to 'long', possible loss o f data cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(13630) : wa rning C4244: 'function' : conversion from 'uintptr_t' to 'unsigned long', possib le loss of data Traceback (most recent call last): File "setup.py", line 113, in "build": cffi_build, File "F:\Python27\lib\distutils\core.py", line 152, in setup dist.run_commands() File "F:\Python27\lib\distutils\dist.py", line 953, in run_commands self.run_command(cmd) File "F:\Python27\lib\distutils\dist.py", line 971, in run_command cmd_obj.ensure_finalized() File "F:\Python27\lib\distutils\cmd.py", line 109, in ensure_finalized self.finalize_options() File "setup.py", line 55, in finalize_options OpenSSLBinding().ffi.verifier.get_extension(), File "J:\projs\cryptography-0.2.1\cryptography\hazmat\bindings\openssl\binding .py", line 83, in __init__ self._ensure_ffi_initialized() File "J:\projs\cryptography-0.2.1\cryptography\hazmat\bindings\openssl\binding .py", line 99, in _ensure_ffi_initialized libraries) File "J:\projs\cryptography-0.2.1\cryptography\hazmat\bindings\utils.py", line 72, in build_ffi ext_package="cryptography", File "F:\Python27\lib\site-packages\cffi\api.py", line 339, in verify lib = self.verifier.load_library() File "F:\Python27\lib\site-packages\cffi\verifier.py", line 74, in load_librar y self._compile_module() File "F:\Python27\lib\site-packages\cffi\verifier.py", line 139, in _compile_m odule outputfilename = ffiplatform.compile(tmpdir, self.get_extension()) File "F:\Python27\lib\site-packages\cffi\ffiplatform.py", line 25, in compile outputfilename = _build(tmpdir, ext) File "F:\Python27\lib\site-packages\cffi\ffiplatform.py", line 50, in _build raise VerificationError('%s: %s' % (e.__class__.__name__, e)) cffi.ffiplatform.VerificationError: CompileError: command '"f:\Program Files (x8 6)\Microsoft Visual Studio 9.0\VC\BIN\amd64\cl.exe"' failed with exit status 2 On 3/3/2014 7:28 PM, Paul Kehrer wrote: > Could you provide the specific error you're seeing on 0.2.1 as well as > whether you're 32 or 64-bit? Our CI infrastructure built wheels > successfully for the 0.2.1 release. > > On Monday, March 3, 2014 at 1:21 PM, Khalid [KAB] wrote: > >> 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 >> >> >> _______________________________________________ >> Cryptography-dev mailing list >> Cryptography-dev at python.org >> https://mail.python.org/mailman/listinfo/cryptography-dev > > > > _______________________________________________ > Cryptography-dev mailing list > Cryptography-dev at python.org > https://mail.python.org/mailman/listinfo/cryptography-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.l.kehrer at gmail.com Tue Mar 4 03:03:25 2014 From: paul.l.kehrer at gmail.com (Paul Kehrer) Date: Mon, 3 Mar 2014 22:03:25 -0400 Subject: [Cryptography-dev] cryptography 0.2.2 Released Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.l.kehrer at gmail.com Tue Mar 4 03:05:30 2014 From: paul.l.kehrer at gmail.com (Paul Kehrer) Date: Mon, 3 Mar 2014 22:05:30 -0400 Subject: [Cryptography-dev] Latest release does not build on Windows In-Reply-To: <5314C0E7.4020108@yahoo.com> References: <5314BA21.5020401@yahoo.com> <5314C0E7.4020108@yahoo.com> Message-ID: <690FA5D26734433BAF7CE67DFD60AEA1@gmail.com> Thanks for the report, we?ve released 0.2.2 which should resolve this issue for you. On another note, do you happen to have a link to/are willing to write a good tutorial about getting 64-bit compilation working under Windows? We?d like to add 64-bit build slaves for 2.6, 2.7, 3.2, and 3.3 but I?ve been unable to get the Windows SDK/Visual Studio to cooperate so far. -Paul On Monday, March 3, 2014 at 1:50 PM, Khalid [KAB] wrote: > I am on Windows 7 x64 using Python 2.7.6 x64: > > J:\projs\cryptography-0.2.1>python > Python 2.7.6 (default, Nov 10 2013, 19:24:24) [MSC v.1500 64 bit (AMD64)] on win > 32 > Type "help", "copyright", "credits" or "license" for more information. > >>> > > Here is the build attempt: > ------------------------------------------------------------- > > J:\projs\cryptography-0.2.1>set LIB=F:\dev\openssl\lib; > > J:\projs\cryptography-0.2.1>set INCLUDE=F:\dev\openssl\include; > > J:\projs\cryptography-0.2.1>python setup.py build > running build > running build_ext > building '_cffi__xcfd0a060xfba2f231' extension > creating J:\projs\cryptography-0.2.1\cryptography\hazmat\primitives\__pycache__\ > Release > creating J:\projs\cryptography-0.2.1\cryptography\hazmat\primitives\__pycache__\ > Release\cryptography > creating J:\projs\cryptography-0.2.1\cryptography\hazmat\primitives\__pycache__\ > Release\cryptography\hazmat > creating J:\projs\cryptography-0.2.1\cryptography\hazmat\primitives\__pycache__\ > Release\cryptography\hazmat\primitives > creating J:\projs\cryptography-0.2.1\cryptography\hazmat\primitives\__pycache__\ > Release\cryptography\hazmat\primitives\__pycache__ > f:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\amd64\cl.exe /c /nolog > o /Ox /MD /W3 /GS- /DNDEBUG -IF:\Python27\include -IF:\Python27\PC /Tccryptograp > hy\hazmat\primitives\__pycache__\_cffi__xcfd0a060xfba2f231.c /FoJ:\projs\cryptog > raphy-0.2.1\cryptography\hazmat\primitives\__pycache__\Release\cryptography\hazm > at\primitives\__pycache__\_cffi__xcfd0a060xfba2f231.obj > _cffi__xcfd0a060xfba2f231.c > f:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\amd64\link.exe /DLL /n > ologo /INCREMENTAL:NO /LIBPATH:F:\Python27\libs /LIBPATH:F:\Python27\PCbuild\amd > 64 /EXPORT:init_cffi__xcfd0a060xfba2f231 J:\projs\cryptography-0.2.1\cryptograph > y\hazmat\primitives\__pycache__\Release\cryptography\hazmat\primitives\__pycache > __\_cffi__xcfd0a060xfba2f231.obj /OUT:J:\projs\cryptography-0.2.1\cryptography\h > azmat\primitives\__pycache__\_cffi__xcfd0a060xfba2f231.pyd /IMPLIB:J:\projs\cryp > tography-0.2.1\cryptography\hazmat\primitives\__pycache__\Release\cryptography\h > azmat\primitives\__pycache__\_cffi__xcfd0a060xfba2f231.lib /MANIFESTFILE:J:\proj > s\cryptography-0.2.1\cryptography\hazmat\primitives\__pycache__\Release\cryptogr > aphy\hazmat\primitives\__pycache__\_cffi__xcfd0a060xfba2f231.pyd.manifest > _cffi__xcfd0a060xfba2f231.obj : warning LNK4197: export 'init_cffi__xcfd0a060xfb > a2f231' specified multiple times; using first specification > Creating library J:\projs\cryptography-0.2.1\cryptography\hazmat\primitives\_ > _pycache__\Release\cryptography\hazmat\primitives\__pycache__\_cffi__xcfd0a060xf > ba2f231.lib and object J:\projs\cryptography-0.2.1\cryptography\hazmat\primitive > s\__pycache__\Release\cryptography\hazmat\primitives\__pycache__\_cffi__xcfd0a06 > 0xfba2f231.exp > running build_ext > building '_cffi__x5fea2bacx4a8b9ec1' extension > f:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\amd64\cl.exe /c /nolog > o /Ox /MD /W3 /GS- /DNDEBUG -IF:\Python27\include -IF:\Python27\PC /Tccryptograp > hy\hazmat\primitives\__pycache__\_cffi__x5fea2bacx4a8b9ec1.c /FoJ:\projs\cryptog > raphy-0.2.1\cryptography\hazmat\primitives\__pycache__\Release\cryptography\hazm > at\primitives\__pycache__\_cffi__x5fea2bacx4a8b9ec1.obj > _cffi__x5fea2bacx4a8b9ec1.c > cryptography\hazmat\primitives\__pycache__\_cffi__x5fea2bacx4a8b9ec1.c(218) : wa > rning C4244: '=' : conversion from 'unsigned __int64' to 'uint8_t', possible los > s of data > f:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\amd64\link.exe /DLL /n > ologo /INCREMENTAL:NO /LIBPATH:F:\Python27\libs /LIBPATH:F:\Python27\PCbuild\amd > 64 /EXPORT:init_cffi__x5fea2bacx4a8b9ec1 J:\projs\cryptography-0.2.1\cryptograph > y\hazmat\primitives\__pycache__\Release\cryptography\hazmat\primitives\__pycache > __\_cffi__x5fea2bacx4a8b9ec1.obj /OUT:J:\projs\cryptography-0.2.1\cryptography\h > azmat\primitives\__pycache__\_cffi__x5fea2bacx4a8b9ec1.pyd /IMPLIB:J:\projs\cryp > tography-0.2.1\cryptography\hazmat\primitives\__pycache__\Release\cryptography\h > azmat\primitives\__pycache__\_cffi__x5fea2bacx4a8b9ec1.lib /MANIFESTFILE:J:\proj > s\cryptography-0.2.1\cryptography\hazmat\primitives\__pycache__\Release\cryptogr > aphy\hazmat\primitives\__pycache__\_cffi__x5fea2bacx4a8b9ec1.pyd.manifest > _cffi__x5fea2bacx4a8b9ec1.obj : warning LNK4197: export 'init_cffi__x5fea2bacx4a > 8b9ec1' specified multiple times; using first specification > Creating library J:\projs\cryptography-0.2.1\cryptography\hazmat\primitives\_ > _pycache__\Release\cryptography\hazmat\primitives\__pycache__\_cffi__x5fea2bacx4 > a8b9ec1.lib and object J:\projs\cryptography-0.2.1\cryptography\hazmat\primitive > s\__pycache__\Release\cryptography\hazmat\primitives\__pycache__\_cffi__x5fea2ba > cx4a8b9ec1.exp > running build_ext > building '_cffi__xd7f460e7x5223a62c' extension > creating J:\projs\cryptography-0.2.1\cryptography\hazmat\bindings\__pycache__\Re > lease > creating J:\projs\cryptography-0.2.1\cryptography\hazmat\bindings\__pycache__\Re > lease\cryptography > creating J:\projs\cryptography-0.2.1\cryptography\hazmat\bindings\__pycache__\Re > lease\cryptography\hazmat > creating J:\projs\cryptography-0.2.1\cryptography\hazmat\bindings\__pycache__\Re > lease\cryptography\hazmat\bindings > creating J:\projs\cryptography-0.2.1\cryptography\hazmat\bindings\__pycache__\Re > lease\cryptography\hazmat\bindings\__pycache__ > f:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\amd64\cl.exe /c /nolog > o /Ox /MD /W3 /GS- /DNDEBUG -IF:\Python27\include -IF:\Python27\PC /Tccryptograp > hy\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c /FoJ:\projs\cryptogra > phy-0.2.1\cryptography\hazmat\bindings\__pycache__\Release\cryptography\hazmat\b > indings\__pycache__\_cffi__xd7f460e7x5223a62c.obj > _cffi__xd7f460e7x5223a62c.c > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(1535) : war > ning C4048: different array subscripts : 'unsigned char (*)[]' and 'unsigned cha > r (*)[32]' > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(1536) : war > ning C4048: different array subscripts : 'unsigned char (*)[]' and 'unsigned cha > r (*)[32]' > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(1560) : war > ning C4048: different array subscripts : 'unsigned char (*)[]' and 'unsigned cha > r (*)[48]' > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4410) : war > ning C4308: negative integral constant converted to unsigned type > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4429) : war > ning C4308: negative integral constant converted to unsigned type > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4448) : war > ning C4308: negative integral constant converted to unsigned type > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4467) : war > ning C4308: negative integral constant converted to unsigned type > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4486) : war > ning C4308: negative integral constant converted to unsigned type > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4505) : war > ning C4308: negative integral constant converted to unsigned type > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4524) : war > ning C4308: negative integral constant converted to unsigned type > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4543) : war > ning C4308: negative integral constant converted to unsigned type > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4562) : war > ning C4308: negative integral constant converted to unsigned type > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4581) : war > ning C4308: negative integral constant converted to unsigned type > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(5702) : err > or C2065: 'EVP_R_DISABLED_FOR_FIPS' : undeclared identifier > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(5702) : err > or C2065: 'EVP_R_DISABLED_FOR_FIPS' : undeclared identifier > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(5703) : err > or C2065: 'EVP_R_DISABLED_FOR_FIPS' : undeclared identifier > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(5704) : err > or C2065: 'EVP_R_DISABLED_FOR_FIPS' : undeclared identifier > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(5705) : err > or C2065: 'EVP_R_DISABLED_FOR_FIPS' : undeclared identifier > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(5707) : err > or C2065: 'EVP_R_DISABLED_FOR_FIPS' : undeclared identifier > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(8473) : war > ning C4308: negative integral constant converted to unsigned type > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(11004) : wa > rning C4267: 'function' : conversion from 'size_t' to 'long', possible loss of d > ata > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(11004) : wa > rning C4267: 'function' : conversion from 'size_t' to 'unsigned long', possible > loss of data > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(11031) : wa > rning C4267: 'function' : conversion from 'size_t' to 'long', possible loss of d > ata > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(11031) : wa > rning C4267: 'function' : conversion from 'size_t' to 'unsigned long', possible > loss of data > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(13630) : wa > rning C4244: 'function' : conversion from 'uintptr_t' to 'long', possible loss o > f data > cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(13630) : wa > rning C4244: 'function' : conversion from 'uintptr_t' to 'unsigned long', possib > le loss of data > Traceback (most recent call last): > File "setup.py", line 113, in > "build": cffi_build, > File "F:\Python27\lib\distutils\core.py", line 152, in setup > dist.run_commands() > File "F:\Python27\lib\distutils\dist.py", line 953, in run_commands > self.run_command(cmd) > File "F:\Python27\lib\distutils\dist.py", line 971, in run_command > cmd_obj.ensure_finalized() > File "F:\Python27\lib\distutils\cmd.py", line 109, in ensure_finalized > self.finalize_options() > File "setup.py", line 55, in finalize_options > OpenSSLBinding().ffi.verifier.get_extension(), > File "J:\projs\cryptography-0.2.1\cryptography\hazmat\bindings\openssl\binding > .py", line 83, in __init__ > self._ensure_ffi_initialized() > File "J:\projs\cryptography-0.2.1\cryptography\hazmat\bindings\openssl\binding > .py", line 99, in _ensure_ffi_initialized > libraries) > File "J:\projs\cryptography-0.2.1\cryptography\hazmat\bindings\utils.py", line > 72, in build_ffi > ext_package="cryptography", > File "F:\Python27\lib\site-packages\cffi\api.py", line 339, in verify > lib = self.verifier.load_library() > File "F:\Python27\lib\site-packages\cffi\verifier.py", line 74, in load_librar > y > self._compile_module() > File "F:\Python27\lib\site-packages\cffi\verifier.py", line 139, in _compile_m > odule > outputfilename = ffiplatform.compile(tmpdir, self.get_extension()) > File "F:\Python27\lib\site-packages\cffi\ffiplatform.py", line 25, in compile > outputfilename = _build(tmpdir, ext) > File "F:\Python27\lib\site-packages\cffi\ffiplatform.py", line 50, in _build > raise VerificationError('%s: %s' % (e.__class__.__name__, e)) > cffi.ffiplatform.VerificationError: CompileError: command '"f:\Program Files (x8 > 6)\Microsoft Visual Studio 9.0\VC\BIN\amd64\cl.exe"' failed with exit status 2 > > > > On 3/3/2014 7:28 PM, Paul Kehrer wrote: > > Could you provide the specific error you?re seeing on 0.2.1 as well as whether you?re 32 or 64-bit? Our CI infrastructure built wheels successfully for the 0.2.1 release. > > > > On Monday, March 3, 2014 at 1:21 PM, Khalid [KAB] wrote: > > > > > 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 > > > > > > > > > _______________________________________________ > > > Cryptography-dev mailing list > > > Cryptography-dev at python.org (mailto:Cryptography-dev at python.org) > > > https://mail.python.org/mailman/listinfo/cryptography-dev > > > > > > > > > > > > > > > > > > > _______________________________________________ Cryptography-dev mailing list Cryptography-dev at python.org (mailto:Cryptography-dev at python.org) https://mail.python.org/mailman/listinfo/cryptography-dev > _______________________________________________ > Cryptography-dev mailing list > Cryptography-dev at python.org (mailto:Cryptography-dev at python.org) > https://mail.python.org/mailman/listinfo/cryptography-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From khabkr at yahoo.com Tue Mar 4 10:32:11 2014 From: khabkr at yahoo.com (Khalid [KAB]) Date: Tue, 04 Mar 2014 11:32:11 +0200 Subject: [Cryptography-dev] Latest release does not build on Windows In-Reply-To: <690FA5D26734433BAF7CE67DFD60AEA1@gmail.com> References: <5314BA21.5020401@yahoo.com> <5314C0E7.4020108@yahoo.com> <690FA5D26734433BAF7CE67DFD60AEA1@gmail.com> Message-ID: <53159D9B.6040700@yahoo.com> Setting up Visual Studio and the various Windows SDKs were done so long ago that I cannot remember what exact steps are needed off the top of my head. But I remember that the order of installing-- i.e., the patches and SDKs-- did make a difference. Also after a quick search I remember there was also a compiler update needed, although I think that was for VS2010 Express. Here are the links: [1] http://ta.speot.is/2012/04/09/visual-studio-2010-sp1-windows-sdk-7-1-install-order/ [2] http://blogs.msdn.com/b/windowssdk/archive/2008/02/22/using-visual-c-2008-express-with-the-windows-sdk-detailed-version.aspx Good luck Khalid On 3/4/2014 4:05 AM, Paul Kehrer wrote: > Thanks for the report, we've released 0.2.2 which should resolve this > issue for you. > > On another note, do you happen to have a link to/are willing to write > a good tutorial about getting 64-bit compilation working under > Windows? We'd like to add 64-bit build slaves for 2.6, 2.7, 3.2, and > 3.3 but I've been unable to get the Windows SDK/Visual Studio to > cooperate so far. > > -Paul > > On Monday, March 3, 2014 at 1:50 PM, Khalid [KAB] wrote: > >> I am on Windows 7 x64 using Python 2.7.6 x64: >> >> J:\projs\cryptography-0.2.1>python >> Python 2.7.6 (default, Nov 10 2013, 19:24:24) [MSC v.1500 64 bit >> (AMD64)] on win >> 32 >> Type "help", "copyright", "credits" or "license" for more information. >> >>> >> >> Here is the build attempt: >> ------------------------------------------------------------- >> >> J:\projs\cryptography-0.2.1>set LIB=F:\dev\openssl\lib; >> >> J:\projs\cryptography-0.2.1>set INCLUDE=F:\dev\openssl\include; >> >> J:\projs\cryptography-0.2.1>python setup.py build >> running build >> running build_ext >> building '_cffi__xcfd0a060xfba2f231' extension >> creating >> J:\projs\cryptography-0.2.1\cryptography\hazmat\primitives\__pycache__\ >> Release >> creating >> J:\projs\cryptography-0.2.1\cryptography\hazmat\primitives\__pycache__\ >> Release\cryptography >> creating >> J:\projs\cryptography-0.2.1\cryptography\hazmat\primitives\__pycache__\ >> Release\cryptography\hazmat >> creating >> J:\projs\cryptography-0.2.1\cryptography\hazmat\primitives\__pycache__\ >> Release\cryptography\hazmat\primitives >> creating >> J:\projs\cryptography-0.2.1\cryptography\hazmat\primitives\__pycache__\ >> Release\cryptography\hazmat\primitives\__pycache__ >> f:\Program Files (x86)\Microsoft Visual Studio >> 9.0\VC\BIN\amd64\cl.exe /c /nolog >> o /Ox /MD /W3 /GS- /DNDEBUG -IF:\Python27\include -IF:\Python27\PC >> /Tccryptograp >> hy\hazmat\primitives\__pycache__\_cffi__xcfd0a060xfba2f231.c >> /FoJ:\projs\cryptog >> raphy-0.2.1\cryptography\hazmat\primitives\__pycache__\Release\cryptography\hazm >> at\primitives\__pycache__\_cffi__xcfd0a060xfba2f231.obj >> _cffi__xcfd0a060xfba2f231.c >> f:\Program Files (x86)\Microsoft Visual Studio >> 9.0\VC\BIN\amd64\link.exe /DLL /n >> ologo /INCREMENTAL:NO /LIBPATH:F:\Python27\libs >> /LIBPATH:F:\Python27\PCbuild\amd >> 64 /EXPORT:init_cffi__xcfd0a060xfba2f231 >> J:\projs\cryptography-0.2.1\cryptograph >> y\hazmat\primitives\__pycache__\Release\cryptography\hazmat\primitives\__pycache >> __\_cffi__xcfd0a060xfba2f231.obj >> /OUT:J:\projs\cryptography-0.2.1\cryptography\h >> azmat\primitives\__pycache__\_cffi__xcfd0a060xfba2f231.pyd >> /IMPLIB:J:\projs\cryp >> tography-0.2.1\cryptography\hazmat\primitives\__pycache__\Release\cryptography\h >> azmat\primitives\__pycache__\_cffi__xcfd0a060xfba2f231.lib >> /MANIFESTFILE:J:\proj >> s\cryptography-0.2.1\cryptography\hazmat\primitives\__pycache__\Release\cryptogr >> aphy\hazmat\primitives\__pycache__\_cffi__xcfd0a060xfba2f231.pyd.manifest >> _cffi__xcfd0a060xfba2f231.obj : warning LNK4197: export >> 'init_cffi__xcfd0a060xfb >> a2f231' specified multiple times; using first specification >> Creating library >> J:\projs\cryptography-0.2.1\cryptography\hazmat\primitives\_ >> _pycache__\Release\cryptography\hazmat\primitives\__pycache__\_cffi__xcfd0a060xf >> ba2f231.lib and object >> J:\projs\cryptography-0.2.1\cryptography\hazmat\primitive >> s\__pycache__\Release\cryptography\hazmat\primitives\__pycache__\_cffi__xcfd0a06 >> 0xfba2f231.exp >> running build_ext >> building '_cffi__x5fea2bacx4a8b9ec1' extension >> f:\Program Files (x86)\Microsoft Visual Studio >> 9.0\VC\BIN\amd64\cl.exe /c /nolog >> o /Ox /MD /W3 /GS- /DNDEBUG -IF:\Python27\include -IF:\Python27\PC >> /Tccryptograp >> hy\hazmat\primitives\__pycache__\_cffi__x5fea2bacx4a8b9ec1.c >> /FoJ:\projs\cryptog >> raphy-0.2.1\cryptography\hazmat\primitives\__pycache__\Release\cryptography\hazm >> at\primitives\__pycache__\_cffi__x5fea2bacx4a8b9ec1.obj >> _cffi__x5fea2bacx4a8b9ec1.c >> cryptography\hazmat\primitives\__pycache__\_cffi__x5fea2bacx4a8b9ec1.c(218) >> : wa >> rning C4244: '=' : conversion from 'unsigned __int64' to 'uint8_t', >> possible los >> s of data >> f:\Program Files (x86)\Microsoft Visual Studio >> 9.0\VC\BIN\amd64\link.exe /DLL /n >> ologo /INCREMENTAL:NO /LIBPATH:F:\Python27\libs >> /LIBPATH:F:\Python27\PCbuild\amd >> 64 /EXPORT:init_cffi__x5fea2bacx4a8b9ec1 >> J:\projs\cryptography-0.2.1\cryptograph >> y\hazmat\primitives\__pycache__\Release\cryptography\hazmat\primitives\__pycache >> __\_cffi__x5fea2bacx4a8b9ec1.obj >> /OUT:J:\projs\cryptography-0.2.1\cryptography\h >> azmat\primitives\__pycache__\_cffi__x5fea2bacx4a8b9ec1.pyd >> /IMPLIB:J:\projs\cryp >> tography-0.2.1\cryptography\hazmat\primitives\__pycache__\Release\cryptography\h >> azmat\primitives\__pycache__\_cffi__x5fea2bacx4a8b9ec1.lib >> /MANIFESTFILE:J:\proj >> s\cryptography-0.2.1\cryptography\hazmat\primitives\__pycache__\Release\cryptogr >> aphy\hazmat\primitives\__pycache__\_cffi__x5fea2bacx4a8b9ec1.pyd.manifest >> _cffi__x5fea2bacx4a8b9ec1.obj : warning LNK4197: export >> 'init_cffi__x5fea2bacx4a >> 8b9ec1' specified multiple times; using first specification >> Creating library >> J:\projs\cryptography-0.2.1\cryptography\hazmat\primitives\_ >> _pycache__\Release\cryptography\hazmat\primitives\__pycache__\_cffi__x5fea2bacx4 >> a8b9ec1.lib and object >> J:\projs\cryptography-0.2.1\cryptography\hazmat\primitive >> s\__pycache__\Release\cryptography\hazmat\primitives\__pycache__\_cffi__x5fea2ba >> cx4a8b9ec1.exp >> running build_ext >> building '_cffi__xd7f460e7x5223a62c' extension >> creating >> J:\projs\cryptography-0.2.1\cryptography\hazmat\bindings\__pycache__\Re >> lease >> creating >> J:\projs\cryptography-0.2.1\cryptography\hazmat\bindings\__pycache__\Re >> lease\cryptography >> creating >> J:\projs\cryptography-0.2.1\cryptography\hazmat\bindings\__pycache__\Re >> lease\cryptography\hazmat >> creating >> J:\projs\cryptography-0.2.1\cryptography\hazmat\bindings\__pycache__\Re >> lease\cryptography\hazmat\bindings >> creating >> J:\projs\cryptography-0.2.1\cryptography\hazmat\bindings\__pycache__\Re >> lease\cryptography\hazmat\bindings\__pycache__ >> f:\Program Files (x86)\Microsoft Visual Studio >> 9.0\VC\BIN\amd64\cl.exe /c /nolog >> o /Ox /MD /W3 /GS- /DNDEBUG -IF:\Python27\include -IF:\Python27\PC >> /Tccryptograp >> hy\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c >> /FoJ:\projs\cryptogra >> phy-0.2.1\cryptography\hazmat\bindings\__pycache__\Release\cryptography\hazmat\b >> indings\__pycache__\_cffi__xd7f460e7x5223a62c.obj >> _cffi__xd7f460e7x5223a62c.c >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(1535) >> : war >> ning C4048: different array subscripts : 'unsigned char (*)[]' and >> 'unsigned cha >> r (*)[32]' >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(1536) >> : war >> ning C4048: different array subscripts : 'unsigned char (*)[]' and >> 'unsigned cha >> r (*)[32]' >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(1560) >> : war >> ning C4048: different array subscripts : 'unsigned char (*)[]' and >> 'unsigned cha >> r (*)[48]' >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4410) >> : war >> ning C4308: negative integral constant converted to unsigned type >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4429) >> : war >> ning C4308: negative integral constant converted to unsigned type >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4448) >> : war >> ning C4308: negative integral constant converted to unsigned type >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4467) >> : war >> ning C4308: negative integral constant converted to unsigned type >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4486) >> : war >> ning C4308: negative integral constant converted to unsigned type >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4505) >> : war >> ning C4308: negative integral constant converted to unsigned type >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4524) >> : war >> ning C4308: negative integral constant converted to unsigned type >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4543) >> : war >> ning C4308: negative integral constant converted to unsigned type >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4562) >> : war >> ning C4308: negative integral constant converted to unsigned type >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(4581) >> : war >> ning C4308: negative integral constant converted to unsigned type >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(5702) >> : err >> or C2065: 'EVP_R_DISABLED_FOR_FIPS' : undeclared identifier >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(5702) >> : err >> or C2065: 'EVP_R_DISABLED_FOR_FIPS' : undeclared identifier >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(5703) >> : err >> or C2065: 'EVP_R_DISABLED_FOR_FIPS' : undeclared identifier >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(5704) >> : err >> or C2065: 'EVP_R_DISABLED_FOR_FIPS' : undeclared identifier >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(5705) >> : err >> or C2065: 'EVP_R_DISABLED_FOR_FIPS' : undeclared identifier >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(5707) >> : err >> or C2065: 'EVP_R_DISABLED_FOR_FIPS' : undeclared identifier >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(8473) >> : war >> ning C4308: negative integral constant converted to unsigned type >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(11004) >> : wa >> rning C4267: 'function' : conversion from 'size_t' to 'long', >> possible loss of d >> ata >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(11004) >> : wa >> rning C4267: 'function' : conversion from 'size_t' to 'unsigned >> long', possible >> loss of data >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(11031) >> : wa >> rning C4267: 'function' : conversion from 'size_t' to 'long', >> possible loss of d >> ata >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(11031) >> : wa >> rning C4267: 'function' : conversion from 'size_t' to 'unsigned >> long', possible >> loss of data >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(13630) >> : wa >> rning C4244: 'function' : conversion from 'uintptr_t' to 'long', >> possible loss o >> f data >> cryptography\hazmat\bindings\__pycache__\_cffi__xd7f460e7x5223a62c.c(13630) >> : wa >> rning C4244: 'function' : conversion from 'uintptr_t' to 'unsigned >> long', possib >> le loss of data >> Traceback (most recent call last): >> File "setup.py", line 113, in >> "build": cffi_build, >> File "F:\Python27\lib\distutils\core.py", line 152, in setup >> dist.run_commands() >> File "F:\Python27\lib\distutils\dist.py", line 953, in run_commands >> self.run_command(cmd) >> File "F:\Python27\lib\distutils\dist.py", line 971, in run_command >> cmd_obj.ensure_finalized() >> File "F:\Python27\lib\distutils\cmd.py", line 109, in ensure_finalized >> self.finalize_options() >> File "setup.py", line 55, in finalize_options >> OpenSSLBinding().ffi.verifier.get_extension(), >> File >> "J:\projs\cryptography-0.2.1\cryptography\hazmat\bindings\openssl\binding >> .py", line 83, in __init__ >> self._ensure_ffi_initialized() >> File >> "J:\projs\cryptography-0.2.1\cryptography\hazmat\bindings\openssl\binding >> .py", line 99, in _ensure_ffi_initialized >> libraries) >> File >> "J:\projs\cryptography-0.2.1\cryptography\hazmat\bindings\utils.py", line >> 72, in build_ffi >> ext_package="cryptography", >> File "F:\Python27\lib\site-packages\cffi\api.py", line 339, in verify >> lib = self.verifier.load_library() >> File "F:\Python27\lib\site-packages\cffi\verifier.py", line 74, in >> load_librar >> y >> self._compile_module() >> File "F:\Python27\lib\site-packages\cffi\verifier.py", line 139, in >> _compile_m >> odule >> outputfilename = ffiplatform.compile(tmpdir, self.get_extension()) >> File "F:\Python27\lib\site-packages\cffi\ffiplatform.py", line 25, >> in compile >> outputfilename = _build(tmpdir, ext) >> File "F:\Python27\lib\site-packages\cffi\ffiplatform.py", line 50, >> in _build >> raise VerificationError('%s: %s' % (e.__class__.__name__, e)) >> cffi.ffiplatform.VerificationError: CompileError: command >> '"f:\Program Files (x8 >> 6)\Microsoft Visual Studio 9.0\VC\BIN\amd64\cl.exe"' failed with exit >> status 2 >> >> >> >> On 3/3/2014 7:28 PM, Paul Kehrer wrote: >>> Could you provide the specific error you're seeing on 0.2.1 as well >>> as whether you're 32 or 64-bit? Our CI infrastructure built wheels >>> successfully for the 0.2.1 release. >>> >>> On Monday, March 3, 2014 at 1:21 PM, Khalid [KAB] wrote: >>> >>>> 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 >>>> >>>> >>>> _______________________________________________ >>>> Cryptography-dev mailing list >>>> Cryptography-dev at python.org >>>> https://mail.python.org/mailman/listinfo/cryptography-dev >>> >>> >>> >>> _______________________________________________ >>> Cryptography-dev mailing list >>> Cryptography-dev at python.org >>> https://mail.python.org/mailman/listinfo/cryptography-dev >> >> _______________________________________________ >> Cryptography-dev mailing list >> Cryptography-dev at python.org >> https://mail.python.org/mailman/listinfo/cryptography-dev > > > > _______________________________________________ > Cryptography-dev mailing list > Cryptography-dev at python.org > https://mail.python.org/mailman/listinfo/cryptography-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: From khabkr at yahoo.com Tue Mar 4 13:19:11 2014 From: khabkr at yahoo.com (Khalid [KAB]) Date: Tue, 04 Mar 2014 14:19:11 +0200 Subject: [Cryptography-dev] Latest release does not build on Windows In-Reply-To: <53159D9B.6040700@yahoo.com> References: <5314BA21.5020401@yahoo.com> <5314C0E7.4020108@yahoo.com> <690FA5D26734433BAF7CE67DFD60AEA1@gmail.com> <53159D9B.6040700@yahoo.com> Message-ID: <5315C4BF.2020904@yahoo.com> Also it is worth noting that some versions of Visual Studio are missing stdint.h and inttypes.h (i.e. VS2008). I believe Visual Studio 2010 Express (the one I have access to) includes stdint.h, but not inttypes.h. There is a googlecode project dedicated to providing these missing files in case they are needed: http://code.google.com/p/msinttypes/ Regards Khalid On 3/4/2014 11:32 AM, Khalid [KAB] wrote: > Setting up Visual Studio and the various Windows SDKs were done so > long ago that I cannot remember what exact steps are needed off the > top of my head. But I remember that the order of installing-- i.e., > the patches and SDKs-- did make a difference. Also after a quick > search I remember there was also a compiler update needed, although I > think that was for VS2010 Express. > > Here are the links: > > [1] > http://ta.speot.is/2012/04/09/visual-studio-2010-sp1-windows-sdk-7-1-install-order/ > [2] > http://blogs.msdn.com/b/windowssdk/archive/2008/02/22/using-visual-c-2008-express-with-the-windows-sdk-detailed-version.aspx > > > Good luck > > Khalid > > > On 3/4/2014 4:05 AM, Paul Kehrer wrote: >> Thanks for the report, we've released 0.2.2 which should resolve this >> issue for you. >> >> On another note, do you happen to have a link to/are willing to write >> a good tutorial about getting 64-bit compilation working under >> Windows? We'd like to add 64-bit build slaves for 2.6, 2.7, 3.2, and >> 3.3 but I've been unable to get the Windows SDK/Visual Studio to >> cooperate so far. >> >> -Paul >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From khalid.abubakr at yahoo.com Sun Mar 9 15:51:59 2014 From: khalid.abubakr at yahoo.com (kab) Date: Sun, 09 Mar 2014 14:51:59 -0000 Subject: [Cryptography-dev] Building on Windows 7, 64x Message-ID: <1392259752.84316.YahooMailNeo@web125704.mail.ne1.yahoo.com> 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 >?? 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 From paul.l.kehrer at gmail.com Sun Mar 9 22:51:06 2014 From: paul.l.kehrer at gmail.com (Paul Kehrer) Date: Sun, 9 Mar 2014 17:51:06 -0400 Subject: [Cryptography-dev] Ancient OpenSSL Support Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From terrycwk1994 at gmail.com Mon Mar 10 01:16:15 2014 From: terrycwk1994 at gmail.com (Terry Chia) Date: Mon, 10 Mar 2014 08:16:15 +0800 Subject: [Cryptography-dev] Ancient OpenSSL Support In-Reply-To: References: Message-ID: -1 on this because Fedora is supposed to be a bleeding edge distribution with a 6 month upgrade cycle. We shouldn't be supporting ancient versions of it. The patch is small enough that the user can get it to work and maintain it on his own if he really needs to. I don't think it's a good idea to be landing the patch without officially supporting it because it *might* confuse some people. +1 on documenting the supported OpenSSL versions. On Mon, Mar 10, 2014 at 5:51 AM, Paul Kehrer wrote: > 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 > > _______________________________________________ > Cryptography-dev mailing list > Cryptography-dev at python.org > https://mail.python.org/mailman/listinfo/cryptography-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexs at prol.etari.at Mon Mar 10 09:13:55 2014 From: alexs at prol.etari.at (alexs) Date: Mon, 10 Mar 2014 08:13:55 +0000 Subject: [Cryptography-dev] Ancient OpenSSL Support In-Reply-To: References: Message-ID: <419ec4930d2d69177d5c1b35811baae6@prol.etari.at> I think we should ship it but document that we *require* OpenSSL 0.9.8e and deny all knowledge of any earlier versions. It really has to be made very explicit that we do not support and can not test versions earlier than RedHat EL 5 if we do accept this. If we end up breaking it in future and someone feels like sending us an equally small PR I think we should also accept that. I am entirely OK with us providing zero guarantees about this functionality but still accepting fixes for it. The whole 0.9.8 ABI is pretty stable. It's mostly because we compile from source that we have problems on Linux so I expect most of the changes required to keep 0.9.8b working will be similar simple but tedious conditional binding things. If we in future decide to drop support for an older OpenSSL I think we should just drop all of 0.9.8 at once, but I guess that's a discussion for a different thread. On 09.03.2014 21:51, Paul Kehrer wrote: > 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 From alex.gaynor at gmail.com Mon Mar 10 16:07:18 2014 From: alex.gaynor at gmail.com (Alex Gaynor) Date: Mon, 10 Mar 2014 08:07:18 -0700 Subject: [Cryptography-dev] Ancient OpenSSL Support In-Reply-To: <419ec4930d2d69177d5c1b35811baae6@prol.etari.at> References: <419ec4930d2d69177d5c1b35811baae6@prol.etari.at> Message-ID: +1 on what Alex said. Alex On Mon, Mar 10, 2014 at 1:13 AM, alexs wrote: > I think we should ship it but document that we *require* OpenSSL 0.9.8e > and deny all knowledge of any earlier versions. It really has to be made > very explicit that we do not support and can not test versions earlier than > RedHat EL 5 if we do accept this. > > If we end up breaking it in future and someone feels like sending us an > equally small PR I think we should also accept that. I am entirely OK with > us providing zero guarantees about this functionality but still accepting > fixes for it. > > The whole 0.9.8 ABI is pretty stable. It's mostly because we compile from > source that we have problems on Linux so I expect most of the changes > required to keep 0.9.8b working will be similar simple but tedious > conditional binding things. > > If we in future decide to drop support for an older OpenSSL I think we > should just drop all of 0.9.8 at once, but I guess that's a discussion for > a different thread. > > > On 09.03.2014 21:51, Paul Kehrer wrote: > > 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 >> > _______________________________________________ > Cryptography-dev mailing list > Cryptography-dev at python.org > https://mail.python.org/mailman/listinfo/cryptography-dev > -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero GPG Key fingerprint: 125F 5C67 DFE9 4084 -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.l.kehrer at gmail.com Tue Mar 11 15:55:44 2014 From: paul.l.kehrer at gmail.com (Paul Kehrer) Date: Tue, 11 Mar 2014 10:55:44 -0400 Subject: [Cryptography-dev] Ancient OpenSSL Support In-Reply-To: References: <419ec4930d2d69177d5c1b35811baae6@prol.etari.at> Message-ID: <76B1C5EBB39F4032AE869F39387FE6CB@gmail.com> Okay, voting on the list and in IRC is mildly in favor of merging this but not supporting it. A PR has already landed to explicitly document our minimum supported version (0.9.8e) so unless there are other objections I will merge the PR once the author fixes our review notes and passes our CI. On Monday, March 10, 2014 at 11:07 AM, Alex Gaynor wrote: > +1 on what Alex said. > > Alex > > > On Mon, Mar 10, 2014 at 1:13 AM, alexs wrote: > > I think we should ship it but document that we *require* OpenSSL 0.9.8e and deny all knowledge of any earlier versions. It really has to be made very explicit that we do not support and can not test versions earlier than RedHat EL 5 if we do accept this. > > > > If we end up breaking it in future and someone feels like sending us an equally small PR I think we should also accept that. I am entirely OK with us providing zero guarantees about this functionality but still accepting fixes for it. > > > > The whole 0.9.8 ABI is pretty stable. It's mostly because we compile from source that we have problems on Linux so I expect most of the changes required to keep 0.9.8b working will be similar simple but tedious conditional binding things. > > > > If we in future decide to drop support for an older OpenSSL I think we should just drop all of 0.9.8 at once, but I guess that's a discussion for a different thread. > > > > > > On 09.03.2014 21:51, Paul Kehrer wrote: > > > > > 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 > > _______________________________________________ > > Cryptography-dev mailing list > > Cryptography-dev at python.org (mailto:Cryptography-dev at python.org) > > https://mail.python.org/mailman/listinfo/cryptography-dev > > > > -- > "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) > "The people's good is the highest law." -- Cicero > GPG Key fingerprint: 125F 5C67 DFE9 4084 > _______________________________________________ > Cryptography-dev mailing list > Cryptography-dev at python.org (mailto:Cryptography-dev at python.org) > https://mail.python.org/mailman/listinfo/cryptography-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.l.kehrer at gmail.com Sat Mar 15 13:29:53 2014 From: paul.l.kehrer at gmail.com (Paul Kehrer) Date: Sat, 15 Mar 2014 08:29:53 -0400 Subject: [Cryptography-dev] Cryptography Third Release (0.3) Criteria Message-ID: <3F5DFB294A424A7DAA817C65569EB9E1@gmail.com> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From alex.gaynor at gmail.com Sat Mar 15 17:04:23 2014 From: alex.gaynor at gmail.com (Alex Gaynor) Date: Sat, 15 Mar 2014 09:04:23 -0700 Subject: [Cryptography-dev] Cryptography Third Release (0.3) Criteria In-Reply-To: <3F5DFB294A424A7DAA817C65569EB9E1@gmail.com> References: <3F5DFB294A424A7DAA817C65569EB9E1@gmail.com> Message-ID: This criteria looks ok to me, the only one I'm not up to speed on is the serialization one, everything else looks like it should be landable. Thanks, Alex On Sat, Mar 15, 2014 at 5:29 AM, Paul Kehrer wrote: > 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 > > _______________________________________________ > Cryptography-dev mailing list > Cryptography-dev at python.org > https://mail.python.org/mailman/listinfo/cryptography-dev > > -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero GPG Key fingerprint: 125F 5C67 DFE9 4084 -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.l.kehrer at gmail.com Thu Mar 27 22:23:22 2014 From: paul.l.kehrer at gmail.com (Paul Kehrer) Date: Thu, 27 Mar 2014 16:23:22 -0500 Subject: [Cryptography-dev] cryptography 0.3 Message-ID: <833DD83438DE466BA043D9FC8700F6B6@gmail.com> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From abhishek8816 at gmail.com Fri Mar 28 09:27:58 2014 From: abhishek8816 at gmail.com (Abhishek Ram) Date: Fri, 28 Mar 2014 13:57:58 +0530 Subject: [Cryptography-dev] cryptography 0.3 In-Reply-To: <833DD83438DE466BA043D9FC8700F6B6@gmail.com> References: <833DD83438DE466BA043D9FC8700F6B6@gmail.com> Message-ID: <3A77D48A-86EC-45F0-87BA-45B1E8EFDA22@gmail.com> Hi, A quick question does this release support loading of RSA keys, I did not find anything that stated this in the change log. Regards Abhishek Ram On 28-Mar-2014, at 2:53 am, Paul Kehrer wrote: > 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 > _______________________________________________ > Cryptography-dev mailing list > Cryptography-dev at python.org > https://mail.python.org/mailman/listinfo/cryptography-dev From paul.l.kehrer at gmail.com Fri Mar 28 14:03:08 2014 From: paul.l.kehrer at gmail.com (Paul Kehrer) Date: Fri, 28 Mar 2014 08:03:08 -0500 Subject: [Cryptography-dev] cryptography 0.3 In-Reply-To: <3A77D48A-86EC-45F0-87BA-45B1E8EFDA22@gmail.com> References: <833DD83438DE466BA043D9FC8700F6B6@gmail.com> <3A77D48A-86EC-45F0-87BA-45B1E8EFDA22@gmail.com> Message-ID: Unfortunately loading keys did not make it into this release, but will be in the fourth release. Right now the only way to load a key is to obtain the n, p, q, d, e, dmp1, dmq1, iqmp integer values and pass them directly to the RSAPrivateKey constructor. On Friday, March 28, 2014 at 3:27 AM, Abhishek Ram wrote: > Hi, > > A quick question does this release support loading of RSA keys, I did not find anything that stated this in the change log. > > Regards > Abhishek Ram > On 28-Mar-2014, at 2:53 am, Paul Kehrer wrote: > > > 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 > > _______________________________________________ > > Cryptography-dev mailing list > > Cryptography-dev at python.org (mailto:Cryptography-dev at python.org) > > https://mail.python.org/mailman/listinfo/cryptography-dev > > > > > _______________________________________________ > Cryptography-dev mailing list > Cryptography-dev at python.org (mailto:Cryptography-dev at python.org) > https://mail.python.org/mailman/listinfo/cryptography-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: