On 1/27/2014 10:28, Kathleen Wilson wrote:
Draft Design Doc posted by Ryan Sleevi regarding Chrome migrating from
NSS to OpenSSL:
https://docs.google.com/document/d/1ML11ZyyMpnAr6clIAwWrXD53pQgNR-DppMYwt9XvE6s/edit?pli=1
Switching to OpenSSL, however, has the opportunity to bring
On 31/01/14 10:24, Julien Pierre wrote:
On 1/27/2014 10:28, Kathleen Wilson wrote:
Draft Design Doc posted by Ryan Sleevi regarding Chrome migrating from
NSS to OpenSSL:
https://docs.google.com/document/d/1ML11ZyyMpnAr6clIAwWrXD53pQgNR-DppMYwt9XvE6s/edit?pli=1
Strange that PKCS#11 support
On Fri, January 31, 2014 9:18 am, Alan Braggins wrote:
On 31/01/14 10:24, Julien Pierre wrote:
On 1/27/2014 10:28, Kathleen Wilson wrote:
Draft Design Doc posted by Ryan Sleevi regarding Chrome migrating from
NSS to OpenSSL:
softoken also isn't a complete implementation of a PKCS#11 module. It's
just good enough to be used by NSS, not good enough to be used by other
PKCS#11 platforms. It's disturbing that it's never been completed. It's
more disturbing because the keys I might have in FIPS softoken can't be
used in
Ryan,
On 1/31/2014 10:28, Ryan Sleevi wrote:
I tried not to write too much on the negatives of NSS or OpenSSL,
because both are worthy of long rants, but I'm surprised to hear
anyone who has worked at length with PKCS#11 - like Oracle has (and
Sun before) - would be particularly praising it.
5 matches
Mail list logo