The problem is resolved - thanks to all the folks who responded. This is
a great alias!
The issue was with the path of the PKCS11 module and also the fact that
my version of NSS was looking for secmod.db whereas my db was named
secmodule.db (coming from Netscape 4.79).
thanks,
Mythili.
--- Begin Message ---
Mythili Subharam wrote:
Hi,
Any more info on this? I also tried netscape 4.79 (with nss-3.6.1 for
signtool) and still see the same problem. "modutil" on secmodule.db (for
netscape 4.79) does not list the external module either (the ibutton
module). However, it does show up in the browser's "cryptographic
modules". Is the browser reading these from a different file - not
secmodule.db?
thanks,
Mythili.
Is there a 'path' problem? Sometimes PKCS #11 modules are installed with
and implicit path. When you run apps in different directories, they
don't see the module because it's not in their path.
Bob Relyea wrote:
Mythili Subharam wrote:
Does netscape signtool support mozilla's cert8.db or only the older
cert7.db? I tried using signtool to sign a jar using an object signing
cert on a smart card (iButton), but signtool is not recognizing the
card. The card (and the object signing cert on it) show up in the
mozilla browser correctly but are not visible through signtool. I am
using signtool that comes with NSS_3_9_1.
NSS_3_9_1 should support cert8.db. If you are using an iButton, however,
you will also need secmod.db as well. When you specify the certificate
name, specify {token}:{certname} where {token} is the token name for
your iButton and {certname} is the label on your certificate.
bob
thanks,
Mythili.
_______________________________________________
mozilla-crypto mailing list
[EMAIL PROTECTED]
http://mail.mozilla.org/listinfo/mozilla-crypto
_______________________________________________
mozilla-crypto mailing list
[EMAIL PROTECTED]
http://mail.mozilla.org/listinfo/mozilla-crypto
--- End Message ---
