[xmlsec] Re: Stack Traces re: crypto nss

Edward Shallow ed.shallow at rogers.com
Sat Sep 24 12:07:51 PDT 2005


Forgot to mention ... I recompiled xmlsec and verified that it picked up 
mozilla 1.7.10

Edward Shallow wrote:

> I tried upgrading mozilla, mozilla-nss, mozilla-nspr, etc to 1.7.10 
> ... No luck
>
> Still seg faulting whenever I try <KeyName> access to NSS DBs from 
> within template
>
> Would it be possible to add a keycert/p12 to the empty nssdb in 
> testKeys and then test signing with it in the testDSig suite ? This 
> would help prove installation as well.
>
> Thanks again,
> Ed
>
> Edward Shallow wrote:
>
>> Here are 2 stack traces for your review ...
>>
>> This is the test using <KeyName> in the template:
>>
>> (gdb) run sign --crypto nss --crypto-config 
>> /usr/local/src/epm/xmlsec-crypto-config-all --trusted-der 
>> /usr/local/src/epm/keys/nss/cacert.der --output 
>> /usr/local/src/epm/inout/edsign-nss-enveloping-rsa-keyname-x509chain.xml 
>> /usr/local/src/epm/tmpl/signing/tmpl-EPM-nss-enveloping-rsa-keyname-x509chain.xml 
>>
>> The program being debugged has been started already.
>> Start it from the beginning? (y or n) y
>> warning: cannot close "shared object read from target memory": File 
>> in wrong format
>>
>> Starting program: /usr/bin/xmlsec1 sign --crypto nss --crypto-config 
>> /usr/local/src/epm/xmlsec-crypto-config-all --trusted-der 
>> /usr/local/src/epm/keys/nss/cacert.der --output 
>> /usr/local/src/epm/inout/edsign-nss-enveloping-rsa-keyname-x509chain.xml 
>> /usr/local/src/epm/tmpl/signing/tmpl-EPM-nss-enveloping-rsa-keyname-x509chain.xml 
>>
>> Reading symbols from shared object read from target memory...done.
>> Loaded system supplied DSO at 0x43c000
>> [Thread debugging using libthread_db enabled]
>> [New Thread -1208363328 (LWP 3448)]
>> Detaching after fork from child process 3449.
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> [Switching to Thread -1208363328 (LWP 3448)]
>> 0x06a7b166 in SECKEY_GetPublicKeyType () from /usr/lib/libnss3.so
>> (gdb)
>>
>> This seg fault I managed to get from a --pkcs12 test which I hadn't 
>> received before:
>>
>> (gdb) run sign --crypto nss --crypto-config 
>> /usr/local/src/epm/xmlsec-crypto-config-all --pkcs12 
>> /usr/local/src/epm/keys/nss/rsakey.p12 --pwd secret --output 
>> /usr/local/src/epm/inout/edsign-nss-sign-enveloped.xml 
>> /usr/local/src/epm/tmpl/signing/tmpl-EPM-nss-sign-enveloped.xml
>> warning: cannot close "shared object read from target memory": File 
>> in wrong format
>> Starting program: /usr/bin/xmlsec1 sign --crypto nss --crypto-config 
>> /usr/local/src/epm/xmlsec-crypto-config-all --pkcs12 
>> /usr/local/src/epm/keys/nss/rsakey.p12 --pwd secret --output 
>> /usr/local/src/epm/inout/edsign-nss-sign-enveloped.xml 
>> /usr/local/src/epm/tmpl/signing/tmpl-EPM-nss-sign-enveloped.xml
>> Reading symbols from shared object read from target memory...done.
>> Loaded system supplied DSO at 0x14f000
>> [Thread debugging using libthread_db enabled]
>> [New Thread -1209055552 (LWP 3384)]
>> Detaching after fork from child process 3385.
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> [Switching to Thread -1209055552 (LWP 3384)]
>> 0x06a7b166 in SECKEY_GetPublicKeyType () from /usr/lib/libnss3.so
>> (gdb)
>>
>>
>>
>>
>>
>
> _______________________________________________
> xmlsec mailing list
> xmlsec at aleksey.com
> http://www.aleksey.com/mailman/listinfo/xmlsec
>




More information about the xmlsec mailing list