Peter Djalaliev wrote:
Hello Dave,
In your first posting, you said that you have loaded "the relevant
PKCS#11 module". What module are you using? Is it provided with
ProtectTools?
The module ships with ProtectTools as a DLL: ifxtpmck.dll, to be precise.
Otherwise, I read through some of the HP ProtectTools Embedded Security
Manager whitepapers and it seems that the private key and certificate
should both be accessible through the PKCS#11 interfaces...
Cool!
Please tell us when you find the solution, I am quite interested :)
I certainly will. I'm new to cryptography and digital security in
general, and I'm having much more fun than is reasonable sorting it all
out. When I bought my notebook (Compaq nw8440, if you are interested), I
had no idea that it came with an embedded security chip, nor any of the
marvelous software that manages it. I bought the digital certificate
just for fun - I must be mad.
I have a sneaking suspicion now that it is the certificate that is
wonky. It is provided by verisign, but is is special: it is compliant
with Gatekeeper (http://www.verisign.com.au/gatekeeper/), which is an
initiative of the Australian Federal Government.
If only I put print out the details of the certificate and post them
here so that everyone could check them out for me. Gotta be careful,
though, that I don't publish something that should be secret.
_______________________________________________
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto
