No problems as far as I can tell:
$ xmlsec1 verify ./detSigned.xml
OK
SignedInfo References (ok/all): 1/1
Manifests References (ok/all): 0/0
$
Aleksey
On 11/15/10 7:40 PM, G. Ken Holman wrote:
At 2010-11-15 19:20 -0800, Aleksey Sanin wrote:
Apologies, but I don't have a windows box to test it. Any chance you
can get a stack trace?
Sadly, no ... the Windows crash dialogue does not have a lot of options.
I'm only running the command-line version that is freely downloadable
(so that my users can also freely download it).
I did find this associated with the crash:
<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="xmlsec.exe" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="xmlsec.exe" SIZE="43520" CHECKSUM="0x28E18749"
MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0"
LINK_DATE="11/01/2009 18:56:48" UPTO_LINK_DATE="11/01/2009 18:56:48" />
</EXE>
<EXE NAME="libxml2.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="libxml2.dll" SIZE="986112" CHECKSUM="0xAA302274"
MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x20007"
LINK_DATE="10/02/2010 11:27:57" UPTO_LINK_DATE="10/02/2010 11:27:57" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="kernel32.dll" SIZE="989696" CHECKSUM="0x2D998938"
BIN_FILE_VERSION="5.1.2600.5781" BIN_PRODUCT_VERSION="5.1.2600.5781"
PRODUCT_VERSION="5.1.2600.5781" FILE_DESCRIPTION="Windows NT BASE API
Client DLL" COMPANY_NAME="Microsoft Corporation"
PRODUCT_NAME="Microsoft® Windows® Operating System"
FILE_VERSION="5.1.2600.5781 (xpsp_sp3_gdr.090321-1317)"
ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="©
Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0"
VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2"
MODULE_TYPE="WIN32" PE_CHECKSUM="0xFE572" LINKER_VERSION="0x50001"
UPTO_BIN_FILE_VERSION="5.1.2600.5781"
UPTO_BIN_PRODUCT_VERSION="5.1.2600.5781" LINK_DATE="03/21/2009 14:06:58"
UPTO_LINK_DATE="03/21/2009 14:06:58" VER_LANGUAGE="English (United
States) [0x409]" />
</EXE>
</DATABASE>
And the error signature reads:
AppName: xmlsec.exe AppVer: 0.0.0.0 ModName: libxml2.dll
ModVer: 0.0.0.0 Offset: 000a7b5a
But I don't see in all of that anything that might be useful.
When you run the verification in a non-Windows environment, do you get a
clean return code?
Thank you very kindly, Aleksey, for looking at this.
. . . . . . . . . Ken
--
Contact us for world-wide XML consulting & instructor-led training
Crane Softwrights Ltd. http://www.CraneSoftwrights.com/m/
G. Ken Holman mailto:[email protected]
Legal business disclaimers: http://www.CraneSoftwrights.com/legal
_______________________________________________
xmlsec mailing list
[email protected]
http://www.aleksey.com/mailman/listinfo/xmlsec
