Mailman 3 November 2016 - Cryptography-dev

fail to pip install cryptography on redhat 6.5
by Chris H Nov. 25, 2016

Nov. 25, 2016

Hi pyhton team, I have problem to install cryptography and paramiko as following errors. any hints/help are appreciated. system : Host-osver: rhel6.0 OpenSSL 1.0.2d 9 Jul 2015 gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-4) > pip install cryptography Collecting cryptography .... build/temp.linux-x86_64-3.4/_openssl.c:62987: error: expected ')' before 'datasize' build/temp.linux-x86_64-3.4/_openssl.c:62987: error: too many arguments to function 'memset' build/temp.linux-x86_64-3.4/_openssl.c:62997: error: expected ')' before 'datasize' build/temp.linux-x86_64-3.4/_openssl.c:62998: error: expected ')' before 'datasize' build/temp.linux-x86_64-3.4/_openssl.c:62998: error: too many arguments to function 'memset' <snip> build/temp.linux-x86_64-3.4/_openssl.c:55555: error: expected ')' before 'datasize' build/temp.linux-x86_64-3.4/_openssl.c:55556: error: expected ')' before 'datasize' build/temp.linux-x86_64-3.4/_openssl.c:55556: error: too many arguments to function 'memset' build/temp.linux-x86_64-3.4/_openssl.c: In function '_cffi_f_X509_NAME_ENTRY_create_by_OBJ': build/temp.linux-x86_64-3.4/_openssl.c:55603: error: expected ')' before 'datasize' build/temp.linux-x86_64-3.4/_openssl.c:55604: error: expected ')' before 'datasize' build/temp.linux-x86_64-3.4/_openssl.c:55604: error: too many arguments to function 'memset' build/temp.linux-x86_64-3.4/_openssl.c:55614: error: expected ')' before 'datasize' build/temp.linux-x86_64-3.4/_openssl.c:55615: error: expected ')' before 'datasize' build/temp.linux-x86_64-3.4/_openssl.c:55615: error: too many arguments to function 'memset' build/temp.linux-x86_64-3.4/_openssl.c:55629: error: expected ')' before 'datasize' build/temp.linux-x86_64-3.4/_openssl.c:55630: error: expected ')' before 'datasize' <snip> build/temp.linux-x86_64-3.4/_openssl.c:71920: warning: excess elements in struct initializer build/temp.linux-x86_64-3.4/_openssl.c:71920: warning: (near initialization for '_cffi_struct_unions[135]') build/temp.linux-x86_64-3.4/_openssl.c:71920: warning: excess elements in struct initializer build/temp.linux-x86_64-3.4/_openssl.c:71920: warning: (near initialization for '_cffi_struct_unions[135]') error: command 'gcc' failed with exit status 1 ---------------------------------------- Command "/auto/iconatest/users/chhong/ats5.3.0/pyats3.1.1-cel6.50/bin/python3.4 -u -c "import setuptools, tokenize;__file__='/users/chhong/tmp/pip-build-x8ette2c/cryptography/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /users/chhong/tmp/pip-ebuv28m8-record/install-record.txt --single-version-externally-managed --compile --install-headers /auto/iconatest/users/chhong/ats5.3.0/pyats3.1.1-cel6.50/include/site/python3.4/cryptography" failed with error code 1 in /users/chhong/tmp/pip-build-x8ette2c/cryptography/ thanks Chris

1 0

PyCA cryptography 1.6 released
by Paul Kehrer Nov. 22, 2016

Nov. 22, 2016

PyCA cryptography 1.6 has been released to PyPI. 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/): * Deprecated support for OpenSSL 1.0.0. Support will be removed in cryptography 1.7. * Replaced the Python-based OpenSSL locking callbacks with a C version to fix a potential deadlock that could occur if a garbage collection cycle occurred while inside the lock. * Added support for BLAKE2b and BLAKE2s when using OpenSSL 1.1.0. * Added signature_algorithm_oid support to Certificate. * Added signature_algorithm_oid support to CertificateSigningRequest. * Added signature_algorithm_oid support to CertificateRevocationList. * Added support for Scrypt when using OpenSSL 1.1.0. * Added a workaround to improve compatibility with Python application bundling tools like PyInstaller and cx_freeze. * Added support for generating a random_serial_number(). * Added support for encoding IPv4Network and IPv6Network in X.509 certificates for use with NameConstraints. * Added public_bytes() to Name. * Added RelativeDistinguishedName * DistributionPoint now accepts RelativeDistinguishedName for relative_name. Deprecated use of Name as relative_name. * Name now accepts an iterable of RelativeDistinguishedName. RDNs can be accessed via the rdns attribute. When constructed with an iterable of NameAttribute, each attribute becomes a single-valued RDN. * Added derive_private_key(). * Added support for signing and verifying RSA, DSA, and ECDSA signatures with Prehashed digests. Due to the volume of changes in this release the switch to bundling OpenSSL 1.1.0 in the macOS and Windows wheels has been pushed back to version 1.8. 1.7 is tentatively planned to be out in the next 2-3 weeks with some large features that didn't make the cut for this release. -Paul Kehrer (reaperhulk)

1 0

Message authentication and integrity
by Darren S. Nov. 20, 2016

Nov. 20, 2016

Hi, Working on part of a project where there's no requirement for confidentiality, but do need to verify message authentication and integrity. The case is a simple multi-node system where a client component makes a request of another component using an HTTP request. The transport does not currently implement SSL/TLS. The request recipient simply needs to be certain that an authorized/known client issued the request. Each node is under the same administrative control/owner and a secure channel such as SSH may be used for setting up pre-shared keys. What python cryptography recipe is suitable for this? Fernet appears to be geared around symmetric encryption although shared secrets also work for authentication and this seems to be stated when discussing cryptography.fernet.InvalidToken if the token "does not have a valid signature." I'd like to avoid any PKI for the time being, so in addition to cryptography's support we also note PyNaCl digital signatures [1] and the standard library's hmac [2] module. Asymmetric keys as implemented in [1] seem suited. And the native availability and relative simplicity of [2] are also attractive. For this sort of thing, does the cryptography library provide anything that using pre-shared keys and transmitting the computed HMAC with the message wouldn't solve? Do either of these approaches have any significant issues that using public-key message signing would solve? [1] https://pynacl.readthedocs.io/en/latest/signing/ [2] https://docs.python.org/3/library/hmac.html Thanks, -- Darren Spruell phatbuckett(a)gmail.com

1 0

Failed: Cryptography (latest)
by Read the Docs Nov. 19, 2016

Nov. 19, 2016

Build Failed for Cryptography (latest) Error: Version locked, retrying in 5 minutes. You can find out more about this failure here: https://readthedocs.org/projects/cryptography/builds/4691963/ 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

How to encrypt-decrypt a file?
by Virgil Stokes Nov. 13, 2016

Nov. 13, 2016

I have looked at all the documentation and postings that I could find on cryptography and still have been unable to find how to use it with file(s). Anyone's help on this would be greatly appreciated. --V

2 1

PyCA cryptography 1.5.3 released
by Paul Kehrer Nov. 6, 2016

Nov. 6, 2016

PyCA cryptography 1.5.3 has been released to PyPI. 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: SECURITY ISSUE: Fixed a bug where HKDF would return an empty byte-string if used with a length less than algorithm.digest_size. Credit to Markus Döring for reporting the issue. -Paul Kehrer (reaperhulk)

1 0