<p>It was libxml2 used by Apple in Common Programs and by Pidgin the IM client. One has to be carefull about .dll search order on Windows.<br>
Thanks Ed</p>
<div class="gmail_quote">On Jan 13, 2012 12:51 AM, "Aleksey Sanin" <<a href="mailto:aleksey@aleksey.com">aleksey@aleksey.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
You are probably right, the problem is in the runtime libs. Can you check and compare the versions for MS C runtime dlls?<br>
<br>
Another idea is something like antivirus (or virus) that modifies<br>
the executable code while loading it in memory.<br>
<br>
Aleksey<br>
<br>
On 1/12/12 3:53 PM, EdShallow wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Aleksey,<br>
<br>
I have had this xmlsec application (now at 1.2.18) working for<br>
several years without incident on Windows XP, Vista, and even Windows 7.<br>
<br>
However on selected machines that I run the application on, I get an I/O<br>
error related to buffer flushing and C14N canonicalization. This only<br>
happens on certain Windows XP machines and I think it is related to some<br>
run-time executable (.dll or exe) outside my environment.<br>
<br>
Here is the summary trace of what comes out on the console .... note<br>
where there error occurs between xmlSecDSigCtxInitialize and<br>
xmlSecDSigCtxSign<br>
<br>
input buffer follows .... write to stdout from my application<br>
<br>
<?xml version="1.0"?><br>
<Data><br>
<SubData1><br>
<SubSubData1 MimeType="text/plain">This is the data to be<br>
signed.</SubSubData1><br>
<SubSubData2 MimeType="text/plain">This is the data to be<br>
signed.</SubSubData2><br>
<SubSubData3 MimeType="text/plain">This is the data to be<br>
signed.</SubSubData3><br>
</SubData1><br>
<SubData2>This is the data to be signed.</SubData2><br>
<SubData3>This is the data to be signed.</SubData3><br>
<dsig:Signature xmlns:dsig="<a href="http://www.w3.org/2000/09/xmldsig#" target="_blank">http://www.w3.org/<u></u>2000/09/xmldsig#</a>"><br>
<dsig:SignedInfo><br>
<dsig:CanonicalizationMethod<br>
Algorithm="<a href="http://www.w3.org/2001/10/xml-exc-c14n#" target="_blank">http://www.w3.org/<u></u>2001/10/xml-exc-c14n#</a>"/><br>
<dsig:SignatureMethod<br>
Algorithm="<a href="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256" target="_blank">http://www.w3.org/<u></u>2001/04/xmldsig-more#rsa-<u></u>sha256</a>"/><br>
<dsig:Reference URI=""><br>
<dsig:Transforms><br>
<dsig:Transform<br>
Algorithm="<a href="http://www.w3.org/2000/09/xmldsig#enveloped-signature" target="_blank">http://www.w3.org/<u></u>2000/09/xmldsig#enveloped-<u></u>signature</a>"/><br>
</dsig:Transforms><br>
<dsig:DigestMethod Algorithm="<a href="http://www.w3.org/2001/04/xmlenc#sha256" target="_blank">http://www.w3.org/<u></u>2001/04/xmlenc#sha256</a>"/><br>
<dsig:DigestValue/><br>
</dsig:Reference><br>
</dsig:SignedInfo><br>
<dsig:SignatureValue/><br>
<dsig:KeyInfo><br>
<dsig:KeyName>Shallow, Ed</dsig:KeyName><br>
<dsig:X509Data><dsig:<u></u>X509Certificate/><dsig:<u></u>X509IssuerSerial/><br>
</dsig:X509Data><br>
</dsig:KeyInfo><br>
</dsig:Signature></Data><br>
<br>
after xmlSecDSigCtxCreate .... write to stdout from my app<br>
after xmlSecDSigCtxInitialize .... write to stfout from my app<br>
<br>
I/O error : flush error<br>
C14N error : Internal error : flushing output buffer<br>
<br>
after xmlSecDSigCtxSign .... write to stdout from my app<br>
<br>
2012/01/12 18:36:53 INFO Sign with TransactionID 00000000 completed on<br>
thread 1 with Status ===> 1716 and ErrorMessage<br>
==> Failed to create signature Invalid algorithm specified. Error<br>
occurred in function xmlSecDSigCtxSign at line 303<br>
relating to xmlSecDSigCtxSigantureProcessN<u></u>ode<br> Document length 429.<br>
<br>
Any ideas which .dll .exe may be missing, wrong version, etc ....<br>
<br>
Many thanks . . .<br>
<br>
Ed<br>
<br>
--<br>
Ed's Contact Information:<br>
Mobile Phone: <a href="tel:613-852-6410" value="+16138526410" target="_blank">613-852-6410</a><br>
Gmail: <a href="mailto:ed.shallow@gmail.com" target="_blank">ed.shallow@gmail.com</a> <mailto:<a href="mailto:ed.shallow@gmail.com" target="_blank">ed.shallow@gmail.com</a>><br>
VOIP Address: <a href="mailto:107529@sip.ca1.voip.ms" target="_blank">107529@sip.ca1.voip.ms</a> <mailto:<a href="mailto:107529@sip.ca1.voip.ms" target="_blank">107529@sip.ca1.voip.ms</a><u></u>><br>
VOIP DID#: <a href="tel:613-458-5004" value="+16134585004" target="_blank">613-458-5004</a><br>
Skype ID: edward.shallow<br>
Home Phone: <a href="tel:613-482-2090" value="+16134822090" target="_blank">613-482-2090</a><br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
xmlsec mailing list<br>
<a href="mailto:xmlsec@aleksey.com" target="_blank">xmlsec@aleksey.com</a><br>
<a href="http://www.aleksey.com/mailman/listinfo/xmlsec" target="_blank">http://www.aleksey.com/<u></u>mailman/listinfo/xmlsec</a><br>
</blockquote>
</blockquote></div>