Mailman 3 May 2017 - Cryptography-dev

PyCA cryptography 1.9 released
by Paul Kehrer May 30, 2017

May 30, 2017

PyCA cryptography 1.8 (and 1.8.1) has been released to PyPI. cryptography includes both high level recipes and low level interfaces to common cryptographic algorithms such as symmetric ciphers, message digests, and key derivation functions. We support Python 2.6-2.7, Python 3.3+, and PyPy. Changelog: * BACKWARDS INCOMPATIBLE: Elliptic Curve signature verification no longer returns True on success. This brings it in line with the interface’s documentation, and our intent. The correct way to use verify() has always been to check whether or not InvalidSignature was raised. * BACKWARDS INCOMPATIBLE: Dropped support for macOS 10.7 and 10.8. * BACKWARDS INCOMPATIBLE: The minimum supported PyPy version is now 5.3. * Python 3.3 support has been deprecated, and will be removed in the next cryptography release. * Add support for providing tag during GCM finalization via finalize_with_tag(). * Fixed an issue preventing cryptography from compiling against LibreSSL 2.5.x. * Added key_size convenience methods for determining the bit size of a secret scalar for an elliptic curve. * Accessing an unrecognized extension marked critical on an X.509 object will no longer raise an UnsupportedExtension exception, instead an UnrecognizedExtension object will be returned. This behavior was based on a poor reading of the RFC, unknown critical extensions only need to be rejected on certificate verification. * The CommonCrypto backend has been removed. * MultiBackend has been removed. * Whirlpool and RIPEMD160 have been deprecated. Thanks to all the contributors for their hard work on this release! -Paul Kehrer (reaperhulk)

1 0

Failed: Cryptography (latest)
by Read the Docs May 29, 2017

May 29, 2017

Build Failed for Cryptography (latest) You can find out more about this failure here: https://readthedocs.org/projects/cryptography/builds/5488698/ If you have questions, a good place to start is the FAQ: https://docs.readthedocs.org/en/latest/faq.html Keep documenting, Read the Docs -- http://readthedocs.org

1 0

PyCA cryptography 1.8.2 released
by Paul Kehrer May 26, 2017

May 26, 2017

PyCA cryptography 1.8.2 has been released to PyPI. This is a small bug fix release to correct an issue with compilation on OpenSSL 1.1.0f. Changelog: * Fixed a compilation bug affecting OpenSSL 1.1.0f. * Updated Windows and macOS wheels to be compiled against OpenSSL 1.1.0f. -Paul Kehrer (reaperhulk)

1 0

Failed: Cryptography (latest)
by Read the Docs May 25, 2017

May 25, 2017

Build Failed for Cryptography (latest) You can find out more about this failure here: https://readthedocs.org/projects/cryptography/builds/5473660/ If you have questions, a good place to start is the FAQ: https://docs.readthedocs.org/en/latest/faq.html Keep documenting, Read the Docs -- http://readthedocs.org

1 0

Failed: Cryptography (latest)
by Read the Docs May 24, 2017

May 24, 2017

Build Failed for Cryptography (latest) You can find out more about this failure here: https://readthedocs.org/projects/cryptography/builds/5464388/ If you have questions, a good place to start is the FAQ: https://docs.readthedocs.org/en/latest/faq.html Keep documenting, Read the Docs -- http://readthedocs.org

1 0

Failed: Cryptography (latest)
by Read the Docs May 24, 2017

May 24, 2017

Build Failed for Cryptography (latest) You can find out more about this failure here: https://readthedocs.org/projects/cryptography/builds/5464221/ If you have questions, a good place to start is the FAQ: https://docs.readthedocs.org/en/latest/faq.html Keep documenting, Read the Docs -- http://readthedocs.org

1 0

Set padding strategy to use in X.509 certificate signing
by Rob D May 22, 2017

May 22, 2017

I've been using the cryptography library to create a self-signed X.509 certificate, and had difficulty verifying the signature until I discovered that sha256WithRSAEncryption also implies PKCS 1.5, rather than PSS. I didn't expect this, as the docs recommend PSS everywhere, so I thought it would naturally be selected by default. Now I understand that I can verify the signature, but I cannot *choose* the signing algorithm: CertificateBuilder.sign() only allows specification of the *hashing* algorithm. Is the algorithm a choice made by the underlying backend? I'm guessing not, but is there a way to choose the signing algorithm to be used? Otherwise, when I'm verifying the signature, how do I determine the padding strategy: do I have to embed a lookup table storing the padding name for a given signing algorithm OID/name? TIA -- rob

2 1

Failed: Cryptography (ae59061e)
by Read the Docs May 21, 2017

May 21, 2017

Build Failed for Cryptography (latest) You can find out more about this failure here: https://readthedocs.org/projects/cryptography/builds/5450119/ If you have questions, a good place to start is the FAQ: https://docs.readthedocs.org/en/latest/faq.html Keep documenting, Read the Docs -- http://readthedocs.org

1 0

Cross compiling wrong ELF class: ELFCLASS32
by Lars Alex Pedersen May 5, 2017

May 5, 2017

Hope that someone can lead me in the right direction. Trying to cross compile python3-cryptography for an ARM architecture on a x64 host and ends up with: ImportError: /home/laa/git/penguin/ptxdist/platform-tqma28/build-target/cryptography-1.8. 1/.eggs/cffi-1.10.0-py3.5-linux2-arm.egg/_cffi_backend.cpython-35m-arm-linux -gnueabi.so: wrong ELF class: ELFCLASS32 Looks like _cffi_backend.cpython-35m-arm-linux-gnueabi.so if correct but somehow used by a 64bit python during some step? ------------------------------------ target: python3-cryptography.compile ------------------------------------ Installed /home/laa/git/penguin/ptxdist/platform-tqma28/build-target/cryptography-1.8. 1/.eggs/cffi-1.10.0-py3.5-linux2-arm.egg Searching for pycparser Reading https://pypi.python.org/simple/pycparser/ Best match: pycparser 2.17 Downloading https://pypi.python.org/packages/be/64/1bb257ffb17d01f4a38d7ce686809a736837a d4371bcc5c42ba7a715c3ac/pycparser-2.17.tar.gz#md5=ca98dcb50bc1276f230118f6af 5a40c7 Processing pycparser-2.17.tar.gz Writing /tmp/easy_install-3h983a01/pycparser-2.17/setup.cfg Running pycparser-2.17/setup.py -q bdist_egg --dist-dir /tmp/easy_install-3h983a01/pycparser-2.17/egg-dist-tmp-g_kj1xdg warning: no previously-included files matching 'yacctab.*' found under directory 'tests' warning: no previously-included files matching 'lextab.*' found under directory 'tests' warning: no previously-included files matching 'yacctab.*' found under directory 'examples' warning: no previously-included files matching 'lextab.*' found under directory 'examples' zip_safe flag not set; analyzing archive contents... pycparser.ply.__pycache__.yacc.cpython-35: module references __file__ pycparser.ply.__pycache__.yacc.cpython-35: module MAY be using inspect.getsourcefile pycparser.ply.__pycache__.yacc.cpython-35: module MAY be using inspect.stack pycparser.ply.__pycache__.ygen.cpython-35: module references __file__ pycparser.ply.__pycache__.lex.cpython-35: module references __file__ pycparser.ply.__pycache__.lex.cpython-35: module MAY be using inspect.getsourcefile creating /home/laa/git/penguin/ptxdist/platform-tqma28/build-target/cryptography-1.8. 1/.eggs/pycparser-2.17-py3.5.egg Extracting pycparser-2.17-py3.5.egg to /home/laa/git/penguin/ptxdist/platform-tqma28/build-target/cryptography-1.8. 1/.eggs Installed /home/laa/git/penguin/ptxdist/platform-tqma28/build-target/cryptography-1.8. 1/.eggs/pycparser-2.17-py3.5.egg Traceback (most recent call last): File "setup.py", line 335, in <module> **keywords_with_side_effects(sys.argv) File "/home/laa/git/penguin/ptxdist/platform-tqma28/sysroot-host/lib/python3.5/di stutils/core.py", line 108, in setup _setup_distribution = dist = klass(attrs) File "/home/laa/git/penguin/ptxdist/platform-tqma28/sysroot-host/lib/python3.5/si te-packages/setuptools/dist.py", line 272, in __init__ _Distribution.__init__(self,attrs) File "/home/laa/git/penguin/ptxdist/platform-tqma28/sysroot-host/lib/python3.5/di stutils/dist.py", line 281, in __init__ self.finalize_options() File "/home/laa/git/penguin/ptxdist/platform-tqma28/sysroot-host/lib/python3.5/si te-packages/setuptools/dist.py", line 327, in finalize_options ep.load()(self, ep.name, value) File "/home/laa/git/penguin/ptxdist/platform-tqma28/build-target/cryptography-1.8 .1/.eggs/cffi-1.10.0-py3.5-linux2-arm.egg/cffi/setuptools_ext.py", line 188, in cffi_modules add_cffi_module(dist, cffi_module) File "/home/laa/git/penguin/ptxdist/platform-tqma28/build-target/cryptography-1.8 .1/.eggs/cffi-1.10.0-py3.5-linux2-arm.egg/cffi/setuptools_ext.py", line 49, in add_cffi_module execfile(build_file_name, mod_vars) File "/home/laa/git/penguin/ptxdist/platform-tqma28/build-target/cryptography-1.8 .1/.eggs/cffi-1.10.0-py3.5-linux2-arm.egg/cffi/setuptools_ext.py", line 25, in execfile exec(code, glob, glob) File "src/_cffi_src/build_openssl.py", line 94, in <module> extra_link_args=extra_link_args(compiler_type()), File "src/_cffi_src/utils.py", line 61, in build_ffi_for_binding extra_link_args=extra_link_args, File "src/_cffi_src/utils.py", line 69, in build_ffi ffi = FFI() File "/home/laa/git/penguin/ptxdist/platform-tqma28/build-target/cryptography-1.8 .1/.eggs/cffi-1.10.0-py3.5-linux2-arm.egg/cffi/api.py", line 46, in __init__ import _cffi_backend as backend File "/home/laa/git/penguin/ptxdist/platform-tqma28/build-target/cryptography-1.8 .1/.eggs/cffi-1.10.0-py3.5-linux2-arm.egg/_cffi_backend.py", line 7, in <module> __bootstrap__() File "/home/laa/git/penguin/ptxdist/platform-tqma28/build-target/cryptography-1.8 .1/.eggs/cffi-1.10.0-py3.5-linux2-arm.egg/_cffi_backend.py", line 6, in __bootstrap__ imp.load_dynamic(__name__,__file__) File "/home/laa/git/penguin/ptxdist/platform-tqma28/sysroot-host/lib/python3.5/im p.py", line 342, in load_dynamic return _load(spec) ImportError: /home/laa/git/penguin/ptxdist/platform-tqma28/build-target/cryptography-1.8. 1/.eggs/cffi-1.10.0-py3.5-linux2-arm.egg/_cffi_backend.cpython-35m-arm-linux -gnueabi.so: wrong ELF class: ELFCLASS32 /usr/local/lib/ptxdist-2016.08.0/rules/post/ptxd_make_world_compile.make:21: recipe for target '/home/laa/git/penguin/ptxdist/platform-tqma28/state/python3-cryptography.co mpile' failed make: *** [/home/laa/git/penguin/ptxdist/platform-tqma28/state/python3-cryptography.co mpile] Error 1 Best regards Lars Alex Pedersen

1 0