[Cryptography-dev] Signing with Intermediate Certificate not accepted by Browsers

2017-10-01 Thread Julian Meyer
Hi, I woud like to sign a certificate with my internal intermediate (CA) certificate. First I thought the issue was caused by the AuthorityKeyIdentifier Extension without the authority_cert_issuer and authority_cert_serial_number parameters. But as Paul wrote back and I made a few tests, this

Re: [Cryptography-dev] Signing with Intermediate Certificate not accepted by Browsers

2017-10-01 Thread Alex Gaynor
Can you point your certificate at `openssl asn1parse` and compare the string types used in the signature? My guess it that the cryptography generated cert will have UTF8String, and the cert generated by your other software will have PrintableString or some other string time. If yes, good news! Th

Re: [Cryptography-dev] Signing with Intermediate Certificate not accepted by Browsers

2017-10-01 Thread Julian Meyer
Hi Alex,0:d=0 hl=4 l= 964 cons: SEQUENCE 4:d=1 hl=4 l= 684 cons: SEQUENCE 8:d=2 hl=2 l= 3 cons: cont [ 0 ] 10:d=3 hl=2 l= 1 prim: INTEGER :02 13:d=2 hl=2 l= 20 prim: INTEGER :317DC7DB62E6BDDD32EE885BB9BB5792337907E0 35:

Re: [Cryptography-dev] Signing with Intermediate Certificate not accepted by Browsers

2017-10-01 Thread Julian Meyer
Hi, Just a update. I tested it with cryptography==2.1.dev1 and now it is working. So it is exactly this issue, as you guessed it. Thank you very much. Regards, Julian > Am 01.10.2017 um 15:54 schrieb Julian Meyer : > > Hi Alex, > > > Thanks for the fast answer. It seems that you have the ri

Re: [Cryptography-dev] Signing with Intermediate Certificate not accepted by Browsers

2017-10-01 Thread Alex Gaynor
Woo! Good call me :-) We're hoping to have it released in the next week or two. Alex On Sun, Oct 1, 2017 at 10:25 AM, Julian Meyer wrote: > Hi, > > Just a update. I tested it with cryptography==2.1.dev1 and now it is > working. So it is exactly this issue, as you guessed it. > > Thank you very