If you tried to go through the Bridge, and then the NSS library to talk
to the vendor-specific DLL, you will be going through two different
translation layers before you get to the crypto capability on the card.

By going from the Bridge to vendor DLL directly, you save yourself one
layer of translation.  However, you will need to configure each vendor's
library correctly in the Bridge configuration file.

Arshad Noor
StrongAuth, Inc.


----- Original Message -----
From: "David Stutzman" <[EMAIL PROTECTED]>
To: [email protected]
Sent: Friday, October 5, 2007 10:14:58 AM (GMT-0800) America/Los_Angeles
Subject: sun pkcs11 bridge + nss + hw token

I was playing around with accessing NSS through the Sun PKCS11 bridge. 
I was successfully able to generate a keypair and do a signature for 
both RSA and EC (only using the 2 Suite B curves, which I imagine is the 
way the windows build of nss I'm using was made).  I was curious about 
accessing  a different token besides the softoken through the bridge. 
The directions on the java site don't really allude to being able to do 
this:
http://java.sun.com/javase/6/docs/technotes/guides/security/p11guide.html#NSS

If I have the following certdb is it possible to access the DK module 
(and TPKI Token specifically) through the bridge?  Or is this retarded 
and I should just be accessing the token's dll through the bridge 
specifically?

Listing of PKCS #11 Modules
-----------------------------------------------------------
   1. NSS Internal FIPS PKCS #11 Module
          slots: 1 slot attached
         status: loaded

          slot: NSS FIPS 140-2 User Private Key Services
         token: NSS FIPS 140-2 Certificate DB

   2. Root Certs
         library name: ./nssckbi.dll
          slots: 1 slot attached
         status: loaded

          slot:
         token: Builtin Object Token

   3. DK
         library name: dkck201.dll
          slots: 6 slots attached
         status: loaded

          slot: Datakey Reader
         token:

          slot: ActivCard USB Reader V2 0
         token:

          slot: Rainbow Technologies iKeyVirtualReader 0
         token:

          slot: Rainbow Technologies iKeyVirtualReader 1
         token: TPKI Token

          slot: Rainbow Technologies iKeyVirtualReader 2
         token:

          slot: Rainbow Technologies iKeyVirtualReader 3
         token:
-----------------------------------------------------------
_______________________________________________
dev-tech-crypto mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-crypto

_______________________________________________
dev-tech-crypto mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-crypto

Reply via email to