Re: [xmlsec] nssdb problems ... still : (

2005-09-23 Thread Edward Shallow

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@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
___
xmlsec mailing list
xmlsec@aleksey.com
http://www.aleksey.com/mailman/listinfo/xmlsec


Re: [xmlsec] nssdb problems ... still : (

2005-09-23 Thread Edward Shallow

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@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.

Thanks,
Ed
___
xmlsec mailing list
xmlsec@aleksey.com
http://www.aleksey.com/mailman/listinfo/xmlsec


Re: [xmlsec] nssdb problems ... still : (

2005-09-23 Thread Aleksey Sanin



In the meatime can I impose on you to send me your cert8.db keys3.db and 
secmod.db files.

I don't have your keys imported in the nss db. Please get a stack trace
$ gdb xmlsec1
 r xmlsec options

Aleksey
___
xmlsec mailing list
xmlsec@aleksey.com
http://www.aleksey.com/mailman/listinfo/xmlsec


RE: [xmlsec] nssdb problems ... still : (

2005-09-23 Thread Edward Shallow
Actually I am simply testing with your cert/keys from the /tests suite.
Specifically rsakey.p12 i.e. TestRsaKey (nickname) issued from your test CA.

But if you'd rather not ... I'll send you the stack trace soon.

Ed

-Original Message-
From: Aleksey Sanin [mailto:[EMAIL PROTECTED] 
Sent: September 23, 2005 11:54 AM
To: Edward Shallow
Cc: xmlsec@aleksey.com
Subject: Re: [xmlsec] nssdb problems ... still : (



 In the meatime can I impose on you to send me your cert8.db keys3.db 
 and secmod.db files.
I don't have your keys imported in the nss db. Please get a stack trace
$ gdb xmlsec1
 r xmlsec options

Aleksey


___
xmlsec mailing list
xmlsec@aleksey.com
http://www.aleksey.com/mailman/listinfo/xmlsec


Re: [xmlsec] nssdb problems ... still : (

2005-09-22 Thread Aleksey Sanin
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@aleksey.com
http://www.aleksey.com/mailman/listinfo/xmlsec