On Mon, 2015-07-27 at 18:34 +0200, Trick, Daniel wrote:
> Thanks for your reply, Bob!
>
> You said:
> > When you need fine grain control, the application should use
> > issuer/serial number to identify the cert (I think all the mozilla
> > apps have gone to this now)
>
> Well, I agree that it /
Thanks for your reply, Bob!
You said:
When you need fine grain control, the application should use
issuer/serial number to identify the cert (I think all the mozilla
apps have gone to this now)
Well, I agree that it /should/ use the issuer/serial number, which is
supposed to be unique (unlik
On 07/27/2015 12:54 AM, Trick, Daniel wrote:
Thank you a lot for clarification, Kaspar!
So, by design of NSS, all certificates with the same DN will end up
with the same nickname. And the very first certificate with a specific
DN will set the nickname for all other certificates (with that same
Once more, thank you for clarification!
About your patches: I certainly would like to test them. We would *much*
welcome if there was a more flexible (unambiguous) method to configure
the certificate.
But I wonder whether this will be backwards compatible. If we had to
setup the certificate
Thank you a lot for clarification, Kaspar!
So, by design of NSS, all certificates with the same DN will end up with
the same nickname. And the very first certificate with a specific DN
will set the nickname for all other certificates (with that same DN).
Now, I see that this works as long as
5 matches
Mail list logo
