Nelson Bolyard wrote, On 2008-08-03 21:05:
David Allan wrote, On 2008-08-02 19:43:
would you like me to file a bug against that?
Yes, please. You can put this text into the bug report, if you'd like.
I filed this bug about the issue:
https://bugzilla.mozilla.org/show_bug.cgi?id=449087
Nelson Bolyard wrote:
Yes, please. You can put this text into the bug report, if you'd like.
I just walked through that code again more carefully. It's definitely a
bug. It's really a flaw in the design of the private function
pk11_ForceSlot. That function can have any of the following
Thanks for filing it--I've been tied up away from my machine all day
today.
Dave
On Mon, 4 Aug 2008, Nelson Bolyard wrote:
Nelson Bolyard wrote, On 2008-08-03 21:05:
David Allan wrote, On 2008-08-02 19:43:
would you like me to file a bug against that?
Yes, please. You can put this text
David Allan wrote, On 2008-08-02 19:43:
PK11_PubWrapSymKey(CKM_RSA_PKCS_OAEP,
RSAPublicKey,
UnwrappedKey,
WrappedKey);
I'd guess that call failed, right?
Or are you using some third party PKCS#11 module that implements it?
NSS's
Hi all,
I would like to port the client side of a client-server application from
OpenSSL to NSS, but I've hit a snag:
The client creates a symmetric key, encrypts it with the server's public
key and transmits it to the server. The server, over which I have no
control, expects the key to be
On Sat, Aug 2, 2008 at 9:12 AM, David Allan [EMAIL PROTECTED] wrote:
Hi all,
I would like to port the client side of a client-server application from
OpenSSL to NSS, but I've hit a snag:
The client creates a symmetric key, encrypts it with the server's public
key and transmits it to the
Hi Nelson,
Thanks for all the info.
As you probably know, the IETF standards for SSL (TLS), including TLS
1.0
(RFC 2246), TLS 1.1 (RFC 4346), and TLS 1.2 (presently an Internet Draft,
ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-tls-rfc4346-bis-10.txt
), all specify that the
7 matches
Mail list logo