Re: [Cryptography-dev] Cryptography-dev Digest, Vol 48, Issue 1

2017-07-05 Thread Karan karan
Thanks Cory! That explains the issue so looks like the cipher being set by the client just that i need to server support. Thanks, Karan. On Mon, Jul 3, 2017 at 7:35 AM, wrote: > Send Cryptography-dev mailing list submissions to > cryptography-dev@python.org > > To subscribe or unsubscri

[Cryptography-dev] Cert how to set email - x509.RFC822Name(email)

2017-07-05 Thread Karan karan
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 = 'ad...@example.com' subject = issuer = x509.Name([x509.NameAttribute(NameOID.COUNTRY_NAME, country_name), x509.NameAttribute(NameOID.STATE_OR_PROVINCE

Re: [Cryptography-dev] Cert how to set email - x509.RFC822Name(email)

2017-07-05 Thread Paul Kehrer
RFC822Name is a general name type that you'd use within a SubjectAlternativeName. Chances are in this case you actually want the email in the subjectDN, right? If so then you just want to add another element to the list you pass to x509.Name: x509.NameAttribute(NameOID.EMAIL_ADDRESS, email_address

[Cryptography-dev] LDAP string representation of cryptography.x509.Name

2017-07-05 Thread Michael Ströder
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.x

Re: [Cryptography-dev] LDAP string representation of cryptography.x509.Name

2017-07-05 Thread Alex Gaynor
We do not currently have an API for this format. Alex On Jul 5, 2017 2:22 PM, "Michael Ströder" 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 str