Hi all,
I have a path validation/hierarchy question - specifically wondering
about the path validation problems incurred on various clients. (I
realize there's no definite answer besides "test it on all the clients
you care about".)
Imagine a four-cert hierarchy R -> A -> B -> L (Root, Leaf, an
Hello,
I'm facing a new problem regarding pk12util from NSS Tools:
When I import the _first_ certificate of a user into the database with
pk12util, then certificate's name in the NSS database will be:
*NSS Certificate DB:
*
Okay, but as soon as I import the _second_ certificate (or any furth
Okay, I found the solution myself.
It appears that NSS/pk12util is going to add the
"PrivateTokenDescription" prefix if (and only if!) there happens to be a
":" character in the certificate's friendly name.
And this was the case with our certificates for a certain reason. Of
course we couldn
3 matches
Mail list logo