<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2800.1226" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=427165213-26092003>Hi
Aleksey,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=427165213-26092003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=427165213-26092003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=427165213-26092003>I am
compiling the latest versin for Win32. </SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=427165213-26092003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=427165213-26092003>I have
problem with the Openssl. It seems to be missing some archives or there is an
archive with the wrong version.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=427165213-26092003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=427165213-26092003>Anybody who can give me an hint?</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=427165213-26092003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=427165213-26092003>Best
regards</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=427165213-26092003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=427165213-26092003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=427165213-26092003>/NODEFAULTLIB:library<BR>app.obj : error LNK2001:
unresolved external symbol _OPENSSL_add_all_algorithms_<BR>noconf<BR>app.obj :
error LNK2001: unresolved external symbol
_CRYPTO_cleanup_all_ex_data<BR>ciphers.obj : error LNK2001: unresolved external
symbol _EVP_aes_256_cbc<BR>ciphers.obj : error LNK2001: unresolved external
symbol _EVP_aes_192_cbc<BR>ciphers.obj : error LNK2001: unresolved external
symbol _EVP_aes_128_cbc<BR>ciphers.obj : error LNK2001: unresolved external
symbol _EVP_CIPHER_CTX_set_padd<BR>ing<BR>kw_des.obj : error LNK2001: unresolved
external symbol _EVP_CIPHER_CTX_set_paddi<BR>ng<BR>digests.obj : error LNK2001:
unresolved external symbol _EVP_MD_CTX_init<BR>signatures.obj : error LNK2001:
unresolved external symbol _EVP_MD_CTX_init<BR>digests.obj : error LNK2001:
unresolved external symbol _EVP_MD_CTX_cleanup<BR>signatures.obj : error
LNK2001: unresolved external symbol _EVP_MD_CTX_cleanup<BR>hmac.obj : error
LNK2001: unresolved external symbol _HMAC_CTX_init<BR>hmac.obj : error LNK2001:
unresolved external symbol _HMAC_CTX_cleanup<BR>kw_aes.obj : error LNK2001:
unresolved external symbol _AES_encrypt<BR>kw_aes.obj : error LNK2001:
unresolved external symbol _AES_set_encrypt_key<BR>kw_aes.obj : error LNK2001:
unresolved external symbol _AES_decrypt<BR>kw_aes.obj : error LNK2001:
unresolved external symbol _AES_set_decrypt_key<BR>x509.obj : error LNK2001:
unresolved external symbol _ASN1_TIME_check<BR>libeay32.lib(rand_win.obj) :
error LNK2001: unresolved external symbol __imp__Re<BR><A
href="mailto:gQueryValueExA@24">gQueryValueExA@24</A><BR>binaries\libxmlsec-openssl.dll
: fatal error LNK1120: 16 unresolved externals<BR>NMAKE : fatal error U1077:
'link.exe' : return code '0x460'</SPAN></FONT></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> xmlsec-admin@aleksey.com
[mailto:xmlsec-admin@aleksey.com]<B>On Behalf Of </B>Aleksey
Sanin<BR><B>Sent:</B> den 26 september 2003 03:02<BR><B>To:</B> Johannes
Kjos<BR><B>Cc:</B> 'xmlsec@aleksey.com'<BR><B>Subject:</B> Re: SV: [xmlsec]
Using a content ID for URI<BR><BR></FONT></DIV>Well, probably the best option
for you would be option #2: use special URL protocol<BR>in URI attributes like
"cid:<attachment id>" and create custom protocol handlers<BR>for "cid".
Take a look at LibXML2 IO tutorial:<BR><BR> <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> <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 cite=midDD392039E892594289474E1F7234FF190AB38254@hermes.sds.no
type="cite"><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 (<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 [<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></BLOCKQUOTE></BODY></HTML>