<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title></title>
</head>
<body>
Well, "failing to validate reference" simply means that the digests values
do not <br>
match. In this particular case, when Apache calculated digested the c14n
output<br>
both digest and signature values (content of <dsig:DigestValue> and
<dsig:SignatureValue><br>
elements) were *not known* yet. Since as we found this XPath transform includes
<br>
*all* nodes from the input document when you are veryfing the document, <br>
both <dsig:DigestValue> and <dsig:SignatureValue> elements (and
the content of these<br>
elements: the actual base64 encoded digest and signature values!) are *included*
<br>
in the digested data. <br>
And of course, the "sign" and "verify" digests are different because the
digested <br>
data are different :)<br>
<br>
This explains why XMLSec fails to validate this document and also shows that
<br>
any *correct* implementation of XPath transform MUST fail to validate it.<br>
Since you wrote that Apache has no problems with validating this document
I suspect <br>
that Apache does not implement the XPath transform correctly :)<br>
<br>
Probably you can find our more if you can get the c14n output (just before
digesting)<br>
from Apache (something similar to --print-all option in xmlsec). I am sorry
but<br>
I could not help you with it since I gave up on installing Apache toolkit
long time ago (this <br>
was the main reason why I wrote XMLSec library :) ).<br>
<br>
Aleksey<br>
<br>
<br>
<br>
<br>
Moultrie, Ferrell (ISSAtlanta) wrote:<br>
<blockquote type="cite"
cite="mid121184A7DB1F9143BB5E3FACCB54875703FAC8@atlmaiexcp02.iss.local">
<meta http-equiv="Content-Type" content="text/html; ">
<title>Message</title>
<meta content="MSHTML 6.00.2800.1050" name="GENERATOR">
<div><span class="538434501-25072002"><font face="Arial"
color="#0000ff" size="2">Aleksey:</font></span></div>
<div><span class="538434501-25072002"><font face="Arial"
color="#0000ff" size="2"> Yes -- you're right. I even recall reading a
discussion about this in the discussion of enveloped signatures in the specification.
I wondered at the time why they used the convoluted XPath count function
rather than a more direct approach -- now I get it. </font></span></div>
<div><span class="538434501-25072002"><font face="Arial"
color="#0000ff" size="2"> In any event - I suspect that Apache is actually
still signing/verifying the entire document just like XMLSEC is *trying*
to do. So .. I should be able to verify this document also using XMLSEC.
Do you have any idea from the sample our it's output as to why it fails
to validate the Reference? This is *always* the hard part of digital signature
work -- when it doesn't work -- figuring out *why* it failed. What bit is
wrong where ...</font></span></div>
<div><span class="538434501-25072002"><font face="Arial"
color="#0000ff" size="2">Thanks!</font></span></div>
<div><span class="538434501-25072002"><font face="Arial"
color="#0000ff" size="2"> Ferrell</font></span></div>
<blockquote style="margin-right: 0px;">
<div class="OutlookMessageHeader" lang="en-us" dir="ltr"
align="left"><font face="Tahoma" size="2">-----Original Message-----<br>
<b>From:</b> Aleksey Sanin [<a class="moz-txt-link-freetext" href="mailto:aleksey@aleksey.com">mailto:aleksey@aleksey.com</a>] <br>
<b>Sent:</b> Wednesday, July 24, 2002 9:22 PM<br>
<b>To:</b> Moultrie, Ferrell (ISSAtlanta)<br>
<b>Cc:</b> '<a class="moz-txt-link-abbreviated" href="mailto:xmlsec@aleksey.com">xmlsec@aleksey.com</a>'; Dodd, Tim (ISS Atlanta)<br>
<b>Subject:</b> Re: [xmlsec] XMLSEC Reference URI question<br>
<br>
</font></div>
Hi, Moultrie!<br>
<br>
I think that there is a "bug" in the document you provided and Apache<br>
toolkit incorrectly implemented XPath transform. According to the XMLDSig
<br>
spec (<a class="moz-txt-link-freetext"
href="http://www.w3.org/TR/xmldsig-core/#sec-XPath">http://www.w3.org/TR/xmldsig-core/#sec-XPath</a>)
the XPath transform<br>
is evaluated as follows:<br>
<br>
> In other words, the input node-set should be equivalent to the
one that would be created by <br>
> the following process:<br>
> 1. Initialize an XPath evaluation context by setting the initial
node equal to the input XML <br>
> document's root node, and set the context position and size
to 1.<br>
> 2. Evaluate the XPath expression <code>(//. | //@* | //namespace::*)</code><br>
> The evaluation of this expression includes all of the document's
nodes (including comments) in the <br>
> node-set representing the octet stream.<br>
> The transform output is also an XPath node-set. The XPath expression
appearing in the <code>XPath</code> <br>
> parameter is evaluated once for each node in the input node-set.
The result is converted to a <br>
> boolean. If the boolean is true, then the node is included in
the output node-set. If the boolean is <br>
> false, then the node is omitted from the output node-set. <br>
<br>
In our case, the XPath expression in the XPath parameter is "/ISSKeys/Contacts/Contact"<br>
Evaluating this XPath expression returns a non-empty node set and according
to the <br>
XPath spec (<a class="moz-txt-link-freetext"
href="http://www.w3.org/TR/1999/REC-xpath-19991116#booleans">http://www.w3.org/TR/1999/REC-xpath-19991116#booleans</a>)
it is converted <br>
to boolean by a call to the boolean() function. From the same spec, (<a
class="moz-txt-link-freetext"
href="http://www.w3.org/TR/1999/REC-xpath-19991116#function-boolean">http://www.w3.org/TR/1999/REC-xpath-19991116#function-boolean</a>)
<br>
the boolean() function *always* returns true for non-empty node set:<br>
> a node-set is true if and only if it is non-empty <br>
For the document you sent me, this means that the XPath expression from
the XPath <br>
parameter will be "true" for *all* nodes and *all* nodes should be included
in the output.<br>
And this is exactly what XMLSec library returns!<br>
<br>
I totally agree with you that such behavior is absolutely not intuitive
and can cause errors.<br>
XMLDSig working group is now developing a new XPath transform spec (XPath
filter 2) and <br>
this particular issue is fixed there. However, this new spec is not stable
right now and changes<br>
almost every day so I could not recommend to use it in production yet.
<br>
<br>
<br>
Aleksey<br>
<br>
<br>
<br>
Moultrie, Ferrell (ISSAtlanta) wrote:<br>
<blockquote
cite="mid121184A7DB1F9143BB5E3FACCB54875703FAC4@atlmaiexcp02.iss.local"
type="cite">
<pre wrap="">xmlsec verify --print-all --trusted new_export.pem test_allkey_04.xml
I've included the PEM-formatted public key, the XML test document and the
output captured from running the 07/12/02 build of xmlsec plus the one fix
you sent me earlier. Let me know if you need anything else.
Thanks!
Ferrell
-----Original Message-----
From: Aleksey Sanin [<a class="moz-txt-link-freetext"
href="mailto:aleksey@aleksey.com">mailto:aleksey@aleksey.com</a>]
Sent: Wednesday, July 24, 2002 5:48 PM
To: Moultrie, Ferrell (ISSAtlanta)
Cc: '<a class="moz-txt-link-abbreviated"
href="mailto:xmlsec@aleksey.com">xmlsec@aleksey.com</a>'; Dodd, Tim (ISS Atlanta)
Subject: Re: [xmlsec] XMLSEC Reference URI question
I am not sure I clear understand what kind of problem do you have. Will you
mind to send me the file you have problems with?
Thanks,
Aleksey
Moultrie, Ferrell (ISSAtlanta) wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Aleksey:
Ok, I've tried to use an XPath Transform to limit the data being
verified. Unfortunately, it doesn't appear to work. Here's what I see
happening in the
code:
xmlSecTransformXPathReadNode( ) [xpath.c:203] takes the input
xmlSecTransformPtr and upcasts it to a xmlSecXmlTransformPtr. It then
stores the parsed XPath string and the "here" node reference in the
xmlSecXmlTransform object it points to (at least there's checking of
the pointer assignment sanity here).
The caller, xmlSecTransformRead, returns to its caller
xmlSecTransformNodeRead with the pointer to the object containing the
XPath transform information. The transform is further passed back to
xmlSecTransformsNodeRead which calls xmlSecTransformStateUpdate which
discovers that the transform type is xmlSecTransformTypeXml and call
xmlSecTransformCreateXml. This routine, because the file is already
parsed and both curFirstBinTransform and curC14NTransform in the state
object are NULL, does nothing and returns!
This results in the XPath Transform information being parsed and saved
but otherwise ignored. The <Signature> block contains the following
transform which is parsed and ignored in the above case:
<sig:Transform
Algorithm=<a class="moz-txt-link-rfc2396E"
href="http://www.w3.org/TR/1999/REC-xpath-19991116">"http://www.w3.org/TR/1999/REC-xpath-19991116"</a>>
<sig:XPath>/ISSKeys/Contacts/Contact</sig:XPath>
</sig:Transform>
The result is that adding an XPath transform like above, is ignored.
This works properly with the Apache Java tools so I believe that it's a
legal way to construct a reference. Eventually, I'd intended to change
the XPath reference to a here()-relative reference to solve my compound
document problem but this seemed like a quick/easy test --
unfortunately it's not working.
Is this a bug, or, have I missed something else? Since Apache properly
verifies this signature and the code in xmlSecTransformCreateXml seems
to be missing any knowledge of this transform, I'm guessing that it's a
bug -- but I'll appreciate your advice on how to proceed!
Thanks!
Ferrell
=====================================
Ferrell Moultrie (<a class="moz-txt-link-abbreviated"
href="mailto:ferrell@iss.net">ferrell@iss.net</a>)
Software Engineer
Internet Security Systems, Inc.
6303 Barfield Road
Atlanta, Georgia 30328
Phone: 404-236-2600
Direct: 404-236-2849
Fax: 404-236-2632
<a class="moz-txt-link-freetext" href="http://www.iss.net">http://www.iss.net</a>
Internet Security Systems -- The Power to Protect
=====================================
_______________________________________________
xmlsec mailing list
<a class="moz-txt-link-abbreviated" href="mailto:xmlsec@aleksey.com">xmlsec@aleksey.com</a> <a
class="moz-txt-link-freetext"
href="http://www.aleksey.com/mailman/listinfo/xmlsec">http://www.aleksey.com/mailman/listinfo/xmlsec</a>
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<pre wrap=""><hr width="90%" size="4">
xmlSecSignedInfoRead: failed to validate "Reference"
= XMLDSig Result (validate)
== result: FAIL
== sign method: <a class="moz-txt-link-freetext"
href="http://www.w3.org/2000/09/xmldsig#rsa-sha1">http://www.w3.org/2000/09/xmldsig#rsa-sha1</a>
== KEY
=== method: RSAKeyValue
=== key name: NULL
=== key type: Public
=== key origin: x509
=== X509 Certificate
==== Subject Name: /C=US/O=Web Developer/OU=IT/CN=ISS Keygen Test
==== Issuer Name: /C=US/O=Web Developer/OU=IT/CN=ISS Keygen Test
==== Issuer Serial: 3CEF18C2
== SIGNED INFO REFERENCES
=== REFERENCE
==== ref type: SignedInfo Reference
==== result: FAIL
==== digest method: <a class="moz-txt-link-freetext"
href="http://www.w3.org/2000/09/xmldsig#sha1">http://www.w3.org/2000/09/xmldsig#sha1</a>
==== uri:
==== type: NULL
==== id: NULL
==== start buffer:
<ISSKeys Source="ISS Atlanta">
<Contacts>
<Contact>
<Keys Address1="2626 Somewhere Lane" Address2="suite 200A" City="Atlanta" Country="US" Email=<a
class="moz-txt-link-rfc2396E" href="mailto:keys@iss.net">"keys@iss.net"</a> Fax="778-555-1212" Phone="777.555.1212" PostCode="30064" Weburl=<a
class="moz-txt-link-rfc2396E" href="http://web.fubar.net">"http://web.fubar.net"</a>></Keys>
<CustomerRelations Address1="1313 k nowwhere Lane" Address2="suite 300A" City="Atlanta" Country="US" Email=<a
class="moz-txt-link-rfc2396E" href="mailto:customer_relations@iss.net">"customer_relations@iss.net"</a> Fax="778-555-7799" Phone="77 7.555.7788" PostCode="30064" Weburl=<a
class="moz-txt-link-rfc2396E"
href="http://web.customer_relations_iss.net">"http://web.customer_relations_iss.net"</a>></CustomerRelations>
<Support Address1="1234 Anvil Rd." Address2="suite 440B" City="Atlanta" Country="US" Email=<a
class="moz-txt-link-rfc2396E" href="mailto:support@iss.net">"support@iss.net"</a> Fax="778-555-7755" Phone="777.555.7744" PostCode="3 0064" Weburl=<a
class="moz-txt-link-rfc2396E" href="http://web.suport_iss.net">"http://web.suport_iss.net"</a>></Support>
<Version>1.0</Version>
<OCN>163444</OCN>
<Source>ISS Atlanta</Source>
<Serial>AC
C64BB4-A53D-AC83-3E6F-E0AB737DEC9D</Serial>
<Timestamp>2000-06-14 10:34:09</Timestamp>
<sig:Signature xmlns:sig=<a class="moz-txt-link-rfc2396E"
href="http://www.w3.org/2000/09/xmldsig#">"http://www.w3.org/2000/09/xmldsig#"</a>>
<sig:SignedInfo>
<sig:CanonicalizationMethod Algorithm=<a
class="moz-txt-link-rfc2396E"
href="http://www.w3.org/TR/2001/REC-xml-c14n-20010315">"http://www.w3.org/TR/2001/REC-xml-c14n-20010315"</a>></sig:CanonicalizationMethod>
<sig:SignatureMethod Algorithm=<a class="moz-txt-link-rfc2396E"
href="http://www.w3.org/2000/09/xmldsig#rsa-sha1">"http://www.w3.org/2000/09/xmldsig#rsa-sha1"</a>></sig:SignatureMethod>
<sig:Reference URI="">
<sig:Transforms>
<sig:Transform Algorithm=<a class="moz-txt-link-rfc2396E"
href="http://www.w3.org/TR/1999/REC-xpath-19991116">"http://www.w3.org/TR/1999/REC-xpath-19991116"</a>>
<sig:XPath>/ISSKeys/Contacts/Contact</sig:XPath>
</sig:Transform>
<sig:Transform Algorithm=<a class="moz-txt-link-rfc2396E"
href="http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments">"http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments"</a>></sig:Transform>
</sig:Transforms>
<sig:DigestMethod Algorithm=<a class="moz-txt-link-rfc2396E"
href="http://www.w3.org/2000/09/xmldsig#sha1">"http://www.w3.org/2000/09/xmldsig#sha1"</a>></sig:DigestMethod>
<sig:DigestValue>3tPX5xUmcKYHkG3Mv8TBAAYjBIU=</sig:DigestValue>
</sig:Reference>
</sig:SignedInfo>
<sig:SignatureValue>GpbCX9juwQ6k4Hs5j19MSXdtAdxeY9cK06Hb17ugq7f6sIy71gafWWNJ1Na/TKGCrABlgrXWH2VR
asYcPMEmi1RZKDPUzmPAjznKRozjZTS3nn2BrAl1EKLugiqYmer+IG8SOXXTDSiwbmphtsXK+emU
FpUVVxfjLrmk8h6hd4k=</sig:SignatureValue>
<sig:KeyInfo>
<sig:X509Data>
<sig:X509Certificate>
MIICCjCCAXMCBDzvGMIwDQYJKoZIhvcNAQEEBQAwTDELMAkGA1UEBhMCVVMxFjAUBgNVBAoTDVdl
YiBEZXZlbG9wZXIxCzAJBgNVBAsTAklUMRgwFgYDVQQDEw9JU1MgS2V5Z2VuIFRlc3QwHhcNMDIw
NTI1MDQ1MzIyWhcNMjcwMTE0MDQ1MzIyWjBMMQswCQYDVQQGEwJVUzEWMBQGA1UEChMNV2ViIERl
dmVsb3BlcjELMAkGA1UECxMCSVQxGDAWBgNVBAMTD0lTUyBLZXlnZW4gVGVzdDCBnzANBgkqhkiG
9w0BAQEFAAOBjQAwgYkCgYEAy6ACsVtGJ69fkeKxJUlZqUP4FJFDIrkrUEi04c8UAAmC6jxu9+mM
uLD+766Ztrjp/2anYX0QS7ReD+Q78ky3a0nmPDIpAzv8P7tUCBc6Yq11w5c1yHSNDdLPxLlX6+JT
nUXnmXMsfAyC2cnoevc38gfEEkEJnS4iCzUC7WHsNgMCAwEAATANBgkqhkiG9w0BAQQFAAOBgQBy
08EvqGY4QL5GYhuT5Lx26t7V0Tk9bKxzh9YKxtyTLux0sqDFcAQWu1UpjPSOLwgNhE+uaS+CuyIK
wsSzMx84gOIk7/fOS5F7oRk2ouC0QPPhY0iT2wXi9Zhvd6CifjNwvCdDe0tinSeQNfvpo0FSlg8c
GL2eqXYylPEeMvZ5aw==
</sig:X509Certificate>
</sig:X509Data>
<sig:KeyValue>
<sig:RSAKeyValue>
<sig:Modulus>
y6ACsVtGJ69fkeKxJUlZqUP4FJFDIrkrUEi04c8UAAmC6jxu9+mMuLD+766Ztrjp/2anYX0QS7Re
D+Q78ky3a0nmPDIpAzv8P7tUCBc6Yq11w5c1yHSNDdLPxLlX6+JTnUXnmXMsfAyC2cnoevc38gfE
EkEJnS4iCzUC7WHsNgM=
</sig:Modulus>
<sig:Exponent>AQAB</sig:Exponent>
</sig:RSAKeyValue>
</sig:KeyValue>
</sig:KeyInfo>
</sig:Signature>
</Contact>
</Contacts>
<EndUsers>
<EndUser Address1="666 Rockets way" Address2="Apt. B" City="Scienceville" CompanyName="Spacely Sprockets" Country="US" Email=<a
class="moz-txt-link-rfc2396E" href="mailto:gjetson@sprokets.net">"gjetson@sprokets.net"</a> PostCode="" State="Disturbed" SubjectName=FAIL
"George Jetson" Title="Whipping Boy">
<Version>1.0</Version>
<OCN>163444</OCN>
<Source>ISS Atlanta</Source>
<Serial>CE8135D7-8D27-4BC4-BCA6-2DBDE703B6A
E</Serial>
<Timestamp>2000-06-14 10:34:09</Timestamp>
</EndUser>
</EndUsers>
<LicensedModules>
<LicensedModule ContactInfo="ACC64BB4- A53D-AC83-3E6F-E0AB737DEC9D" EndUserInfo="CE8135D7-8D27-4BC4-BCA6-2DBDE703B6AE" Identity="RO" LicenseExpiration="2003-06-14" LicenseType="evaluation" Limit="2147483647" LimitOutOfMaintenance="0" MaintenanceExpiration="2003-06-14">
<Version>1.0</Version>
<OCN>163444</OCN>
<Source>ISS Atlanta</Source>
<Serial>F61BD0F3-D5D9-2F90-A24D-BF989200D712</Serial>
<Timestamp>2000-06-14 10:34:09</Timestamp>
</LicensedModule>
</LicensedModules>
</ISSKeys>
==== end buffer:
= Status:
== Signatures ok: 0
== Signatures fail: 1
== SignedInfo Ref ok: 0
== SignedInfo Ref fail: 1
== Manifest Ref ok: 0
== Manifest Ref fail: 0
Error: operation failed
</pre>
</blockquote>
<br>
</blockquote>
</blockquote>
<br>
</body>
</html>