IN RSA PRIVATE KEY-
MIIEp[...]
-END RSA PRIVATE KEY-
eof
It's unrelated to my original problem, but i'd be glad to understand the
asn1parse tool better :)
Nicolas Pelloux-Prayer
2010/2/18 Dr. Stephen Henson
> On Wed, Feb 17, 2010, Nicolas
The output is the same as "openssl pkcs12 -in "User.p12" -info"
Thanks for your response.
Nicolas Pelloux-Prayer
2010/2/17 Ashok Kumar
> I am not sure if you are using the following command. It parses the
> certs & keys.
>
> #openssl pkcs12 -info -nodes -in
> My question is, does the token's PKI engine just do step 5, or does it do
the crypto parts of both 4 and 5? any additional parts of this sequence .?
I worked with a similar context recently, using a custom hardware pkcs11
token & a custom engine, the only operation handled by the hardware token
entually explain the whys
and hows of this issue please.
Thanks in advance,
Nicolas Pelloux-Prayer
*
>openssl asn1parse -in keyfirst.pem -i -dump
0:d=0 hl=4 l=1189 cons: S
I'm currently working on a similar task during the development of a TLS
client (with client-side authentication), using a PKCS#11 hardware token.
The main problem we encountered is that we cannot access the private key
stored in the token; Therefore we made an engine which implements RSA
signature
