Hi,
Is the patch tested on windows ?
z modifier - I'm not sure that this is portable.
if I remember correctly windows doesn't support this modifier
(at least I was told this as we discussed this for another project)
I'm not exactly sure, but I believe it's an extension of glibc
In message [EMAIL PROTECTED] on Mon, 13 Mar 2006 10:05:38 +0100, [EMAIL
PROTECTED] said:
Stefan.Neis Is the patch tested on windows ?
Stefan.Neis z modifier - I'm not sure that this is portable.
Stefan.Neis
Stefan.Neis if I remember correctly windows doesn't support this
Stefan.Neis
the signature, see http://edelpki.edelweb.fr/
Cela vous permet de charger le certificat de l'autorité;
die Liste mit zurückgerufenen Zertifikaten finden Sie da auch.
--- openssl-SNAP-20060313/ssl/t1_lib.c 2006-03-13 03:00:59.0 +0100
+++ openssl-SNAP-20060313+S/ssl/t1_lib.c2006-03-13
Hi,
Various places in the source say that old des support is going to
be removed before 1.0. I think it's time to move forward.
I think we have 2 options:
- Completly drop the old des support, including des_old.h
- Drop the libdes compatibility, so that it's only compatible
with older openssl
Hi,
The attached patch converts destest.c to use DES_* function
instead of des_* functions. It's the only part of the source
that is still using the old names.
Kurt
Index: crypto/des/destest.c
===
RCS file:
I've just recently put together a C# class library that wraps the crypto DLL via PInvoke. I was wondering if anyone here would be interested in such a thing or if perhaps I should just create a seperate project for it. It has many advantages but the biggest is allowing for ease of use of the
This would be a good thing to have available. I don't believe it
should be in the core OpenSSL code, though, but it could be in
contrib/ -- I would suggest making it available as a separate project
on sourceforge or somewhere.
-Kyle H
On 3/13/06, Frank Laub [EMAIL PROTECTED] wrote:
I've just
On 3/13/06, Richard Levitte - VMS Whacker [EMAIL PROTECTED] wrote:
My stand on this is that it's good that BIO_printf and friends works
in compatible ways with printf, AND it is a good thing to make use of
good extensions that are available elsewhere even if they aren't part
of a formal
Frank
This is a very interesting project. IMHO, there are 2 kinds of APIs we
can provide:
1. A OpenSSL-like one. Original users of OpenSSL may like it.
2. Plugin as a service provider for the .NET crypto framework. Existing
.NET codes will be easily re-configured to use the OpenSSL
