Mailman 3 July 2017 - Cryptography-dev

PyCA cryptography 2.0.2 released
by Paul Kehrer July 27, 2017

July 27, 2017

Hot on the heels of 2.0.1 comes a 2.0.2 with just one change to the manylinux1 wheels: * Marked all symbols as hidden in the ``manylinux1`` wheel to avoid a bug with symbol resolution in certain scenarios. -Paul Kehrer (reaperhulk)

1 0

PyCA cryptography 2.0.1 released
by Paul Kehrer July 26, 2017

July 26, 2017

PyCA cryptography 2.0.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.4+, and PyPy. * Fixed a compilation bug affecting OpenBSD. * Altered the manylinux1 wheels to statically link OpenSSL instead of dynamically linking and bundling the shared object. This should resolve crashes seen when using uwsgi or other binaries that link against OpenSSL independently. * Fixed the stack level for the signer and verifier warnings. -Paul Kehrer (reaperhulk)

1 0

Import Error.
by Deepen Patel July 23, 2017

July 23, 2017

Hi, I got error like Import error. Traceback (most recent call last): File "startnode.py", line 8, in <module> from twisted.conch import manhole, manhole_ssh File "/usr/local/lib/python2.7/dist-packages/twisted/conch/manhole_ssh.py", line 14, in <module> from twisted.conch.ssh import factory, session File "/usr/local/lib/python2.7/dist-packages/twisted/conch/ssh/factory.py", line 18, in <module> from twisted.conch.ssh import (_kex, transport, userauth, connection) File "/usr/local/lib/python2.7/dist-packages/twisted/conch/ssh/transport.py", line 22, in <module> from cryptography.exceptions import UnsupportedAlgorithm ImportError: No module named cryptography.exceptions Currently, I am using virtual environments and in virtual environment this code not run properly. previously, I am running code without virtual environments. it works proper. Await your reply. Regards, Deepen Patel.

2 1

Failed: Cryptography (d3c4ba3a)
by Read the Docs July 20, 2017

July 20, 2017

Build Failed for Cryptography (latest) You can find out more about this failure here: https://readthedocs.org/projects/cryptography/builds/5713885/ 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 July 17, 2017

July 17, 2017

Build Failed for Cryptography (latest) You can find out more about this failure here: https://readthedocs.org/projects/cryptography/builds/5700359/ 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 2.0 released
by Paul Kehrer July 17, 2017

July 17, 2017

PyCA cryptography 2.0 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.4+, and PyPy. * BACKWARDS INCOMPATIBLE: Support for Python 3.3 has been dropped. * We now ship manylinux1 wheels linked against OpenSSL 1.1.0f. These wheels will be automatically used with most Linux distributions if you are running the latest pip. * Deprecated the use of signer on RSAPrivateKey, DSAPrivateKey, and EllipticCurvePrivateKey in favor of sign. * Deprecated the use of verifier on RSAPublicKey, DSAPublicKey, and EllipticCurvePublicKey in favor of verify. * Added support for parsing SignedCertificateTimestamp objects from X.509 certificate extensions. * Added support for ChaCha20Poly1305. * Added support for AESCCM. * Added AESGCM, a “one shot” API for AES GCM encryption. * Added support for X25519 key exchange. * Added support for serializing and deserializing Diffie-Hellman parameters with load_pem_parameters(), load_der_parameters(), and parameter_bytes() . * The extensions attribute on Certificate, CertificateSigningRequest, CertificateRevocationList, and RevokedCertificate now caches the computed Extensions object. There should be no performance change, just a performance improvement for programs accessing the extensions attribute multiple times. Thanks to all the contributors! -Paul Kehrer (reaperhulk)

1 0

Cipher/tls cipher negotiated
by Karan karan July 14, 2017

July 14, 2017

Hi, I'm trying to test different cipher and protocols using the request packages, for which i extend the HTTPAdapter. Here are some of the code snippet i have : https://lukasa.co.uk/2013/01/Choosing_SSL_Version_In_Requests/ and then wrap it in Session object as follows: from ssl import SSLContext ... def create_connection(self, sessionreuse=None): """ Create a http connection over ssl Arguments: Returns: returns the Session object, which can use to be make HTTP call """ if self._ssl_version and self._cipher: self._context = SSLContext(self._ssl_version) self._context.set_ciphers(self._ciphers) cipher_adapter = SSLAdapter({'ssl_context': self._context}) if self._proxy: self._session.update(proxies) self._session.mount('https://', cipher_adapter) return self._session Then i use self._session to make get call. What i need to find is the : - SSL version negotatiated finally - Cipher used by the server. I would appreciate if some one could help out on it. Thanks, Karan.

3 3

Re: [Cryptography-dev] LDAP string representation of cryptography.x509.Name
by Alex Gaynor July 5, 2017

July 5, 2017

We do not currently have an API for this format. Alex On Jul 5, 2017 2:22 PM, "Michael Ströder" <michael(a)stroeder.com> wrote: HI! The only standardized string form for X.509 names is the LDAP "String Representation of Distinguished Names" (see RFC 4514). M2Crypto allows to simply let OpenSSL lib generate such a string representation for a subject or issuer name. Is there something similar available for cryptography.x509.Name? Frankly I couldn't figure out how to directly access oid of cryptography.x509.NameAttribute to write something like this. Ciao, Michael. _______________________________________________ Cryptography-dev mailing list Cryptography-dev(a)python.org https://mail.python.org/mailman/listinfo/cryptography-dev

1 0

LDAP string representation of cryptography.x509.Name
by Michael Ströder July 5, 2017

July 5, 2017

HI! The only standardized string form for X.509 names is the LDAP "String Representation of Distinguished Names" (see RFC 4514). M2Crypto allows to simply let OpenSSL lib generate such a string representation for a subject or issuer name. Is there something similar available for cryptography.x509.Name? Frankly I couldn't figure out how to directly access oid of cryptography.x509.NameAttribute to write something like this. Ciao, Michael.

1 0

Cert how to set email - x509.RFC822Name(email)
by Karan karan July 5, 2017

July 5, 2017

Hi, I'm trying to set the email on the certificate my code below , since its a self signed so the issuer and the subject are same: email = 'admin(a)example.com' subject = issuer = x509.Name([x509.NameAttribute(NameOID.COUNTRY_NAME, country_name), x509.NameAttribute(NameOID.STATE_OR_PROVINCE_NAME, state_name), x509.NameAttribute(NameOID.LOCALITY_NAME, locality_name), x509.NameAttribute(NameOID.ORGANIZATION_NAME, org_name), x509.NameAttribute(NameOID.COMMON_NAME, common_name) ]) *x509.RFC822Name(email)* When i check the certificate details i don't see the email id being set using s_client connect Thanks, Karan.

2 1