[xmlsec] Strange Environmental Problem on certain Windows machines

[Aleksey Sanin]

You are probably right, the problem is in the runtime libs. Can you 
check and compare the versions for MS C runtime dlls?

Another idea is something like antivirus (or virus) that modifies
the executable code while loading it in memory.

Aleksey

On 1/12/12 3:53 PM, EdShallow wrote:
> Hi Aleksey,
>
>        I have had this xmlsec application (now at 1.2.18) working for
> several years without incident on Windows XP, Vista, and even Windows 7.
>
> However on selected machines that I run the application on, I get an I/O
> error related to buffer flushing and C14N canonicalization. This only
> happens on certain Windows XP machines and I think it is related to some
> run-time executable (.dll or exe) outside my environment.
>
> Here is the summary trace of what comes out on the console .... note
> where there error occurs between xmlSecDSigCtxInitialize and
> xmlSecDSigCtxSign
>
> input buffer follows .... write to stdout from my application
>
> <?xml version="1.0"?>
> <Data>
> <SubData1>
> <SubSubData1 MimeType="text/plain">This is the data to be
> signed.</SubSubData1>
> <SubSubData2 MimeType="text/plain">This is the data to be
> signed.</SubSubData2>
> <SubSubData3 MimeType="text/plain">This is the data to be
> signed.</SubSubData3>
> </SubData1>
> <SubData2>This is the data to be signed.</SubData2>
> <SubData3>This is the data to be signed.</SubData3>
> <dsig:Signature xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
> <dsig:SignedInfo>
> <dsig:CanonicalizationMethod
> Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
> <dsig:SignatureMethod
> Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/>
> <dsig:Reference URI="">
> <dsig:Transforms>
> <dsig:Transform
> Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
> </dsig:Transforms>
> <dsig:DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/>
> <dsig:DigestValue/>
> </dsig:Reference>
> </dsig:SignedInfo>
> <dsig:SignatureValue/>
> <dsig:KeyInfo>
> <dsig:KeyName>Shallow, Ed</dsig:KeyName>
> <dsig:X509Data><dsig:X509Certificate/><dsig:X509IssuerSerial/>
> </dsig:X509Data>
> </dsig:KeyInfo>
> </dsig:Signature></Data>
>
> after xmlSecDSigCtxCreate  .... write to stdout from my app
> after xmlSecDSigCtxInitialize .... write to stfout from my app
>
> I/O error : flush error
> C14N error : Internal error : flushing output buffer
>
> after xmlSecDSigCtxSign .... write to stdout from my app
>
> 2012/01/12 18:36:53  INFO Sign with TransactionID 00000000 completed on
> thread 1 with Status ===> 1716 and ErrorMessage
> ==> Failed to create signature  Invalid algorithm specified.   Error
> occurred in function xmlSecDSigCtxSign at line 303
> relating to xmlSecDSigCtxSigantureProcessNode<br> Document length 429.
>
> Any ideas which .dll .exe may be missing, wrong version, etc ....
>
> Many thanks . . .
>
> Ed
>
> --
> Ed's Contact Information:
> Mobile Phone: 613-852-6410
> Gmail: ed.shallow at gmail.com <mailto:ed.shallow at gmail.com>
> VOIP Address: 107529 at sip.ca1.voip.ms <mailto:107529 at sip.ca1.voip.ms>
> VOIP DID#: 613-458-5004
> Skype ID: edward.shallow
> Home Phone: 613-482-2090
>
>
>
> _______________________________________________
> xmlsec mailing list
> xmlsec at aleksey.com
> http://www.aleksey.com/mailman/listinfo/xmlsec