<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title></title>
</head>
<body>
<font size="2"><font face="Arial,sans-serif">Hi Aleksey,<br>
<br>
I've run into a snag with the NSS support for xmlsec. <br>
<br>
After many trials with NSS APIs, and several discussions with NSS core<br>
team, what I've learnt is that there is no API in NSS to import<br>
a STANDALONE private key. In other words, to import the private key<br>
I need the associated public key (serves as a handle to the private key<br>
stored in a PKCS11 token). <br>
<br>
I was hoping to use the test harness as is for NSS, but I can't as of<br>
now.<br>
<br>
This begs the question of why you have only private keys in some<br>
of the test files. Where is the associated public key?. <br>
<br>
I noticed that your tests actually extract the public key out of the<br>
private key imported<br>
(Sign operation:<br>
input : private key file, xml template<br>
output: xml file with public key extracted from pvt key in
<KeyInfo>)<br>
<br>
Is it safe to assume that the public key components are always <br>
available in a private key?. I'm hearing that it is not. Did you
create your private <br>
key files in a special way?.<br>
<br>
thanks,<br>
<br>
-Tej<br>
<br>
</font></font>
</body>
</html>