[xmlsec] MS Crypto API support
Olger Warnier
owarnier@cordys.com
Mon, 7 Apr 2003 14:36:28 +0200
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C2FD02.4F3B8D60
Content-Type: text/plain; charset="iso-8859-1"
Hello to all of the list,
After some wandering through the list, I found some details on the support
for different crypto libraries.
The MS CryptoAPI seems not supported (yet) so I am planning on writing the
integration if someone could help me out a little on the way this should be
done. The structure seems to support compiletime support for the use of
another crypto backend. (is support planned for runtime loaded libraries
(dlopen and so on) ?
I am wondering what the list of functions is I should map/support to get it
to work. (the website documentation doesn't tell a lot on this matter yet).
I am planning to use the mscryptoapi as define and directory. If people have
pointers/ideas please let me know.
Kind Regards,
Olger
**********************************************************************
The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this message
by anyone else is unauthorized. If you are not the intended recipient, any
disclosure, copying, or distribution of the message, or any action or
omission taken by you in reliance on it, is prohibited and may be unlawful.
Please immediately contact the sender if you have received this message in
error.
**********************************************************************
------_=_NextPart_001_01C2FD02.4F3B8D60
Content-Type: text/html; charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1141" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=668402812-07042003><FONT face=Arial size=2>Hello to all of the
list,</FONT></SPAN></DIV>
<DIV><SPAN class=668402812-07042003><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=668402812-07042003><FONT face=Arial size=2>After some wandering
through the list, I found some details on the support for different crypto
libraries.</FONT></SPAN></DIV>
<DIV><SPAN class=668402812-07042003><FONT face=Arial size=2>The MS CryptoAPI
seems not supported (yet) so I am planning on writing the integration if
someone could help me out a little on the way this should be done. The structure
seems to support compiletime support for the use of another crypto backend.
(is support planned for runtime loaded libraries (dlopen and so on)
?</FONT></SPAN></DIV>
<DIV><SPAN class=668402812-07042003><FONT face=Arial size=2>I am wondering what
the list of functions is I should map/support to get it to work. (the
website documentation doesn't tell a lot on this matter yet). I am planning to
use the mscryptoapi as define and directory. If people have pointers/ideas
please let me know.</FONT></SPAN></DIV>
<DIV><SPAN class=668402812-07042003><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=668402812-07042003><FONT face=Arial size=2>Kind
Regards,</FONT></SPAN></DIV>
<DIV><SPAN class=668402812-07042003><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=668402812-07042003><FONT face=Arial
size=2>Olger</FONT></SPAN></DIV>
<DIV><SPAN class=668402812-07042003><FONT face=Arial
size=2></FONT></SPAN> </DIV><FONT SIZE=3><BR>
<BR>
**********************************************************************<BR>
The information in this message is confidential and may be legally<BR>
privileged. It is intended solely for the addressee. Access to this message<BR>
by anyone else is unauthorized. If you are not the intended recipient, any<BR>
disclosure, copying, or distribution of the message, or any action or<BR>
omission taken by you in reliance on it, is prohibited and may be unlawful.<BR>
Please immediately contact the sender if you have received this message in<BR>
error.<BR>
<BR>
**********************************************************************<BR>
</FONT>
</BODY></HTML>
------_=_NextPart_001_01C2FD02.4F3B8D60--