Hi Aleksey,
I've run into a snag with the NSS support for xmlsec.
After many trials with NSS APIs, and several discussions with NSS core
team, what I've learnt is that there is no API in NSS to import
a STANDALONE private key. In other words, to import the private key
I need the associated public key (serves as a handle to the private key
stored in a PKCS11 token).
I was hoping to use the test harness as is for NSS, but I can't as of
now.
This begs the question of why you have only private keys in some
of the test files. Where is the associated public key?.
I noticed that your tests actually extract the public key out of the
private key imported
(Sign operation:
input : private key file, xml template
output: xml file with public key extracted from pvt key in
<KeyInfo>)
Is it safe to assume that the public key components are always
available in a private key?. I'm hearing that it is not. Did you
create your private
key files in a special way?.
thanks,
-Tej
_______________________________________________
xmlsec mailing list
[EMAIL PROTECTED]
http://www.aleksey.com/mailman/listinfo/xmlsec
- Re: [xmlsec] standalone private keys Tejkumar Arora
- Re: [xmlsec] standalone private keys Aleksey Sanin
- Re: [xmlsec] standalone private keys Tejkumar Arora
- Re: [xmlsec] standalone private keys Tejkumar Arora
- Re: [xmlsec] standalone private keys Aleksey Sanin
- Re: [xmlsec] standalone private keys Tejkumar Arora
- Re: [xmlsec] standalone private keys Aleksey Sanin
