[xmlsec] nssdb problems ... still : (

Edward Shallow ed.shallow at rogers.com
Fri Sep 23 07:51:46 PDT 2005

Edward Shallow wrote:

> Aleksey Sanin wrote:
>>> 1) and 2) above work fine with pkcs#12 based keys, but as soon as I 
>>> switch to the nssdb-resident equivalent I am unsuccessful.
>> Can you run 3rd test under gdb and get a stack trace?
>> Aleksey
>> _______________________________________________
>> xmlsec mailing list
>> xmlsec at aleksey.com
>> http://www.aleksey.com/mailman/listinfo/xmlsec
> Yes, I will do that soon. Just as a postscript, if it helps you. It 
> seems it will always seg fault unless you have x509 first in the 
> --enabled-key-data list
> example: --enabled-key-data x509,key-name ==> no seg fault
> example: --enabled-key-data key-name,x509 ==> seg fault
> Even when there is no seg fault, however, I always get error=45:key is 
> not found
> I'll send you the stack trace.
> Ed
In the meatime can I impose on you to send me your cert8.db keys3.db and 
secmod.db files.

I would like to rule out the nssdb as the culprit here.


More information about the xmlsec mailing list