[xmlsec] Verify on Microsoft-produced sig

[Edward Shallow]

Aleksey,
 =20
    Yes I did this (see below). It looks like the transform in fact did =
not
transform anything ?

Ed



=3D=3D PreDigest data - start buffer:
<my:myFields
xmlns:my=3D"http://schemas.microsoft.com/office/infopath/2003/myXSD/2003-=
04-12
T15:07:25" xml:lang=3D"en-us">
        <my:OrderNumber>1234</my:OrderNumber>
        <my:txtName>Edward Shallow</my:txtName>
        <my:intCustomerNumber
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance">12345678</my:intC=
ustom
erNumber>
        <my:signatures1></my:signatures1>
</my:myFields>
=3D=3D PreDigest data - end buffer




-----Original Message-----
From: Aleksey Sanin [mailto:aleksey@aleksey.com]=20
Sent: August 29, 2003 12:21 PM
To: Edward Shallow
Cc: xmlsec@aleksey.com

It does not look like it's a problem with undefined ID attributes. If =
you
run xmlsec command line utility with "--store-references" flag you'll =
see
that we could not verify the first reference. It's has an xslt transform =
and
with "--store-references" flag you can see the result of processing this
transform:
  =20
    <my:myFields
xmlns:my=3D"http://schemas.microsoft.com/office/infopath/2003/myXSD/2003-=
04-12
T15:07:25"=20
xml:lang=3D"en-us">
        <my:OrderNumber>1234</my:OrderNumber>
        <my:txtName>Edward Shallow</my:txtName>
        <my:intCustomerNumber
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance">12345678</my:intC=
ustom
erNumber>
        <my:signatures1></my:signatures1>
    </my:myFields>

This is the data that goes into digest and after that digests do not =
match.
I would suspect that there is an interop problem between MS xslt engine =
and
libxslt.
It would be helpfull if you can apply the same xslt template to the same
data using MS engine and compare results.

Aleksey