Nelson B Bolyard wrote:

Please file a bug in bugzilla.mozilla.org about that.
Product: NSS
Component: Libraries
Version: whatever version you're using

I just added the bug here:

https://bugzilla.mozilla.org/show_bug.cgi?id=453364

The gdb trace of how I got there is included, along with the key variable values along the way.

Not immediately obvious.
Here are some questions that may help identify the cause.

What was the value of keyItem.len ?

24 (corresponding to the 192 bit cipher).

Are you using any PKCS#11 modules besides NSS's own modules?

Not that I am aware of.

Do you possibly have a module marked as preferred ("default") for 3DES
that doesn't actually do 3DES?

If you were using only NSS's PKCS#11 modules, did you have the Softoken
module in "FIPS mode" ?

The module is initialised as follows:

s = NSS_NoDB_Init(NULL);

The code is a test case, and doesn't do anything else other than encrypt a string, and then try and decrypt the same string.

Changing the encryption mode from MODE_ECB to MODE_CBC, causes the PK11_CreateContextBySymKey function to succeed.

The next function PK11_CipherOp then fails, with the error code "-8192".

This error code isn't recognised by PR_ErrorToName(), and so again, no action can be taken.

Should I log this as a separate bug, or does this error code -8192 have some meaning to NSS?

Regards,
Graham
--

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto

Reply via email to