> do you think there are pieces that aren't yet merged? have you tried using
> the common names with 1.0.2 and they don't work?
Nope, I was just reading through all the tickets to do some basic triage.
I will close this one. Thanks !
___
openssl-dev
0ec6898c67aeddc3c414f3cc1af2275d81329c20
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
> do you think there are pieces that aren't yet merged? have you tried using
> the common names with 1.0.2 and they don't work?
Nope, I was just reading through all the tickets to do some basic triage.
I will close this one. Thanks !
___
openssl-de
On Tue 2016-02-02 14:08:18 -0500, Rich Salz via RT wrote:
> any chance you can refresh your 1.0.2 patch? I'm interested in being able to
> accept the common names but not changing the output for compatibility..
I am too :)
it looks like it was already merged, though, as
0ec6898c67aeddc3c414f3cc1a
DKG,
any chance you can refresh your 1.0.2 patch? I'm interested in being able to
accept the common names but not changing the output for compatibility..
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
___
openssl-dev mailing list
To unsubscribe: https
