[xmlsec] Problem with multiple X509Certificates
fcosta75 at gmail.com
Wed Nov 17 12:19:03 PST 2010
Yes, I have.
XMLSEC file_: ..\src\list.c line: 184 func: xmlSecPtrListCopy, errorObject:
, errorSubject: dst->id == src->id, reason: 100, msg:
XMLSEC file_: ..\src\xmldsig.c line: 1335 func:
xmlSecDSigReferenceCtxInitialize, errorObject: , errorSubject:
xmlSecPtrListCopy, reason: 1, msg:
XMLSEC file_: ..\src\xmldsig.c line: 1269 func:
xmlSecDSigReferenceCtxCreate, errorObject: , errorSubject:
xmlSecDSigReferenceCtxInitialize, reason: 1, msg:
XMLSEC file_: ..\src\xmldsig.c line: 781 func:
xmlSecDSigCtxProcessSignedInfoNode, errorObject: , errorSubject:
xmlSecDSigReferenceCtxCreate, reason: 1, msg:
XMLSEC file_: ..\src\xmldsig.c line: 547 func:
xmlSecDSigCtxProcessSignatureNode, errorObject: , errorSubject:
xmlSecDSigCtxProcessSignedInfoNode, reason: 1, msg:
XMLSEC file_: ..\src\xmldsig.c line: 303 func: xmlSecDSigCtxSign,
errorObject: , errorSubject: xmlSecDSigCtxSigantureProcessNode, reason: 1,
2010/11/17 Aleksey Sanin <aleksey at aleksey.com>
> What is the stack trace?
> On 11/17/10 12:01 PM, Flávio Costa wrote:
>> I developed my Delphi application using DLLs downloaded from
>> ftp://ftp.zlatkovic.com/libxml/ and everything was fine on my tests
>> using my company A1 certificate.
>> When deploying to my first customer, his signed XML contained 4 distinct
>> X509Certificate tags. After inspecting my code, I found that this
>> strange error was created by libxmlsec, and some google search lead me
>> to version 1.2.16, which contains a fix for this problem. But zlatkovic
>> only provides binaries for version 1.2.13, so I tried to compile myself.
>> The following was compiled successfully with MS Visual Studio 2010:
>> Using new compiled DLLs, my Delphi code reached the following assert on
>> list.c line 184:
>> xmlSecAssert2(dst->id == src->id, -1);
>> I've tried to compile libxmlsec version 1.2.13 again, but my code only
>> works with zlatkovic's binaries. Every version (1.2.13, 1.2.14, 1.2.15)
>> has this same assertion.
>> Any suggestions?
>> Thanks in advance.
>> xmlsec mailing list
>> xmlsec at aleksey.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the xmlsec