On 08/11/2009 07:11 AM, Rishi Renjith wrote:
Now in NSS.conf I added the following lines to use the hardware
accelarator
NSSNickname "Sun Metaslot:ismc_cert"
NSSCertificateDatabase /opt/SMC/Apache2/nssdb
Now everything is working fine, the requests are getting processed
correctly. But the issue is that the rsaprivate value is not getting
incremented in the kstat -n mca0 output. Which means that it is not
using the hardware accelerator card.
If everything is connecting correctly, then there is only a few
possibilities:
1) You are not using an RSA cipher (possible, but unlikely -- not
possible if you have not other key and cert types).
2) You have a copy of the private key in the softoken.- NSS should
prefer the HW token if the exact cert and key is in both. If the key is
only in one or the other then NSS will use the token that contains that
private key (it has not choice). If NSS is using the softoken key it's
likely because:
2a) There is a second cert with the same subject as the one in your
token with a valid public key, and NSS is prefering that cert (probably
because of issuance or key usage reasons).
2b) You don't have the private key in the token (I noted that your
setup did not import any private keys, you used certutil to import your
cert -- which just imports certs, not private keys. You'll want to use
pk12util to import a PKCS #12 package with both the cert and the key).
NOTE: you can solve 2a by deleting the private key in softoken ---
however if your problem is 2b) that means you will loose your private
key. You may want to use pk12util to back it up first.
3) If you are using RSA, and you have not RSA private keys in the
softoken database, and you are connecting correctly -- then you *MUST*
be using the token (or some token) as NSS could never do the private key
operation without the private key. In that case I would suspect your
counter.
bob
--
dev-tech-crypto mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-crypto