SV: [xmlsec] Using a content ID for URI

Aleksey Sanin aleksey@aleksey.com
Fri, 26 Sep 2003 00:01:56 -0700


This is a multi-part message in MIME format.
--------------020703080908070104020506
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Well, probably the best option for you would be option #2: use special 
URL protocol
in URI attributes like "cid:<attachment id>" and create custom protocol 
handlers
for "cid". Take a look at LibXML2 IO tutorial:

     http://xmlsoft.org/xmlio.html

and xmlsec API reference:

     http://www.aleksey.com/xmlsec/api/xmlsec-io.html

And do not forget to register your protocol handlers in both xmlsec and 
libxml2.

Aleksey


Johannes Kjos wrote:

>Ok, I will try to explain once more :)
>
>My secapp is a toolkit to support XMLDsig signing MIME message, there are
>two or more mime parts and the first part is SOAP (<header> and <body>), the
>other mime parts are attachments. These attachments are signed and the
><Signature> is placed inside the SOAP <header>. My secapp only relates and
>thereby returns the SOAP message to the calling application which deals with
>the mime packing and so on. So, when signing an attachment, the calling
>application has to give my secapp a cid and the filepath (it's all filebased
>for a reason not to mention here) for the file to sign, insert the cid in
><SignedInfo> make a digest (and put it in <DigestValue>) of the file with
>filepath, and then sign <SignedInfo>. The reason the cid is signed and not
>the filepath is because my secapp don't deal with the attachment in the
>mimemessage, the calling application does. 
>So when verifying the callig app will search through the attachments and
>when it finds a cid it will give the filepath and the cid to my secapp (the
>rest of the <References> in the <Signature> will be resolved by xmlsec in
>normal manner). My secapp will make a list of these mappings and hopefully
>in some way make the xmlsec to understand that the <SignatureValue> is a
>signature over the current <SignedInfo> but the <DigestValue> of the
>references with the cids is from the files with filepath given by the
>mappings....I know this is working e.g. in the java lib IAIK...
>
>I think this is a version of ebXML.
>
>Best regards,
>Johannes
>
>
>
>-----Opprinnelig melding-----
>Fra: Aleksey Sanin [mailto:aleksey@aleksey.com]
>Sendt: 25. september 2003 17:41
>Til: Johannes Kjos
>Kopi: 'xmlsec@aleksey.com'
>Emne: Re: [xmlsec] Using a content ID for URI
>
>
>No, it's actually not quite clear but I would try to guess :)
>
>    1) You would like to use "#ID" or any other XPointer expression in 
>URI attributes.
>    Yes, it is possible. Please read section 3.2 from FAQ 
>http://www.aleksey.com/xmlsec/faq.html
>    for the only known common issue about that.
>   
>    2) You need to use custom protocols like URI="cid:something"
>    Yes, it is possible. You would need to register custom protocol 
>handlers in both
>    LibXML2 and xmlsec. Search headers in both libraries for 
>"RegisterProtocol".
>    Protocol handlers in both libraries are exactly the same. LibXML2 
>handlers are used
>    for reading XML files (thus they can automatically do some smart 
>things like gzip/gunzip)
>    and xmlsec protocol handlers are used for reading binary files. Also 
>there is a tutorial'
>    page on LibXML2 web site http://xmlsoft.org about writing IO callbacks.
>
>
>Aleksey
>
>
>Johannes Kjos wrote:
>
>  
>
>>Hello!
>>I'm using xmlsec 0.0.15! And using an upgrade makes a lot of work for me
>>because other project participants have made quit a lot of work in the
>>0.0.15 code. 
>>
>>My question is: Is it possible to make the xmlseclib to use a cid for URI
>>    
>>
>in
>  
>
>>SignedInfo References? E.g.I want the calling app to search through a some
>>blocks of a message, inside them there is cids to be resolved for the cids
>>in the references (the signature is in a header element). The calling app
>>should send e.g. filepath and URI to my secapp and I will make xmlsec to
>>    
>>
>use
>  
>
>>the file for digest but have the cid for that file in SignedInfo when
>>signing - and the other way when verifying.
>>
>>Hope this is understandable...
>>
>>Best regards,
>>Johannes
>>
>>
>>_______________________________________________
>>xmlsec mailing list
>>xmlsec@aleksey.com
>>http://www.aleksey.com/mailman/listinfo/xmlsec
>> 
>>
>>    
>>
>_______________________________________________
>xmlsec mailing list
>xmlsec@aleksey.com
>http://www.aleksey.com/mailman/listinfo/xmlsec
>  
>

--------------020703080908070104020506
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Well, probably the best option for you would be option #2: use special
URL protocol<br>
in URI attributes like "cid:&lt;attachment id&gt;" and create custom
protocol handlers<br>
for "cid". Take a look at LibXML2 IO tutorial:<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp; <a class="moz-txt-link-freetext" href="http://xmlsoft.org/xmlio.html">http://xmlsoft.org/xmlio.html</a><br>
<br>
and xmlsec API reference:<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp; <a class="moz-txt-link-freetext" href="http://www.aleksey.com/xmlsec/api/xmlsec-io.html">http://www.aleksey.com/xmlsec/api/xmlsec-io.html</a><br>
<br>
And do not forget to register your protocol handlers in both xmlsec and
libxml2.<br>
<br>
Aleksey<br>
<br>
<br>
Johannes Kjos wrote:<br>
<blockquote type="cite"
 cite="midDD392039E892594289474E1F7234FF190AB38254@hermes.sds.no">
  <pre wrap="">Ok, I will try to explain once more :)

My secapp is a toolkit to support XMLDsig signing MIME message, there are
two or more mime parts and the first part is SOAP (&lt;header&gt; and &lt;body&gt;), the
other mime parts are attachments. These attachments are signed and the
&lt;Signature&gt; is placed inside the SOAP &lt;header&gt;. My secapp only relates and
thereby returns the SOAP message to the calling application which deals with
the mime packing and so on. So, when signing an attachment, the calling
application has to give my secapp a cid and the filepath (it's all filebased
for a reason not to mention here) for the file to sign, insert the cid in
&lt;SignedInfo&gt; make a digest (and put it in &lt;DigestValue&gt;) of the file with
filepath, and then sign &lt;SignedInfo&gt;. The reason the cid is signed and not
the filepath is because my secapp don't deal with the attachment in the
mimemessage, the calling application does. 
So when verifying the callig app will search through the attachments and
when it finds a cid it will give the filepath and the cid to my secapp (the
rest of the &lt;References&gt; in the &lt;Signature&gt; will be resolved by xmlsec in
normal manner). My secapp will make a list of these mappings and hopefully
in some way make the xmlsec to understand that the &lt;SignatureValue&gt; is a
signature over the current &lt;SignedInfo&gt; but the &lt;DigestValue&gt; of the
references with the cids is from the files with filepath given by the
mappings....I know this is working e.g. in the java lib IAIK...

I think this is a version of ebXML.

Best regards,
Johannes



-----Opprinnelig melding-----
Fra: Aleksey Sanin [<a class="moz-txt-link-freetext" href="mailto:aleksey@aleksey.com">mailto:aleksey@aleksey.com</a>]
Sendt: 25. september 2003 17:41
Til: Johannes Kjos
Kopi: '<a class="moz-txt-link-abbreviated" href="mailto:xmlsec@aleksey.com">xmlsec@aleksey.com</a>'
Emne: Re: [xmlsec] Using a content ID for URI


No, it's actually not quite clear but I would try to guess :)

    1) You would like to use "#ID" or any other XPointer expression in 
URI attributes.
    Yes, it is possible. Please read section 3.2 from FAQ 
<a class="moz-txt-link-freetext" href="http://www.aleksey.com/xmlsec/faq.html">http://www.aleksey.com/xmlsec/faq.html</a>
    for the only known common issue about that.
   
    2) You need to use custom protocols like URI=<a class="moz-txt-link-rfc2396E" href="cid:something">"cid:something"</a>
    Yes, it is possible. You would need to register custom protocol 
handlers in both
    LibXML2 and xmlsec. Search headers in both libraries for 
"RegisterProtocol".
    Protocol handlers in both libraries are exactly the same. LibXML2 
handlers are used
    for reading XML files (thus they can automatically do some smart 
things like gzip/gunzip)
    and xmlsec protocol handlers are used for reading binary files. Also 
there is a tutorial'
    page on LibXML2 web site <a class="moz-txt-link-freetext" href="http://xmlsoft.org">http://xmlsoft.org</a> about writing IO callbacks.


Aleksey


Johannes Kjos wrote:

  </pre>
  <blockquote type="cite">
    <pre wrap="">Hello!
I'm using xmlsec 0.0.15! And using an upgrade makes a lot of work for me
because other project participants have made quit a lot of work in the
0.0.15 code. 

My question is: Is it possible to make the xmlseclib to use a cid for URI
    </pre>
  </blockquote>
  <pre wrap=""><!---->in
  </pre>
  <blockquote type="cite">
    <pre wrap="">SignedInfo References? E.g.I want the calling app to search through a some
blocks of a message, inside them there is cids to be resolved for the cids
in the references (the signature is in a header element). The calling app
should send e.g. filepath and URI to my secapp and I will make xmlsec to
    </pre>
  </blockquote>
  <pre wrap=""><!---->use
  </pre>
  <blockquote type="cite">
    <pre wrap="">the file for digest but have the cid for that file in SignedInfo when
signing - and the other way when verifying.

Hope this is understandable...

Best regards,
Johannes


_______________________________________________
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=""><!---->_______________________________________________
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>
</body>
</html>

--------------020703080908070104020506--