IMHO, it's a crypto library problem. I am not sure I see any reasons
for this "public key as key id" requirement but I do not have pkcs8
format in front of me right now so  I might be wrong. However, I know
that some other crypto libraries can get private key from pkcs8 file
directly and this makes me think that it is possible.

Aleksey

The code I've written does exactly this.... but I did not anticipate
that I wouldn't have an NSS API that allows me to import
an encrypted private key from a p8 file (the current API
requires a public key as a "key id"). I tried to get around it
by using an artificial "key id", importing the private key, and
then extracting the public key and re-importing the private key...
but that didn't work :(.
_______________________________________________ xmlsec mailing list [EMAIL PROTECTED] http://www.aleksey.com/mailman/listinfo/xmlsec

Reply via email to