Re: Windows DLL naming inconsistency

2004-01-26 Thread Andy Polyakov
I entirely agree with the idea of following the standard set in the environment you work in. However, if we look at the file name without the extension, I'm only aware of a naming standard on Unix (libraries start with lib) But what does this naming convention on Unix means *exactly*? Is it

Re: Windows DLL naming inconsistency

2004-01-26 Thread Andy Polyakov
... this MT and debugging naming convention exists exclusively in compiler driver's mind, cl.exe in Microsoft case, and applies I naturally meant mind in quotes:-) Added to this problem, we have the different register sizes on different CPUs (32-bit, 64-bit, and

Re: Windows DLL naming inconsistency

2004-01-26 Thread Richard Levitte - VMS Whacker
In message [EMAIL PROTECTED] on Mon, 26 Jan 2004 12:07:56 +0100, Andy Polyakov [EMAIL PROTECTED] said: appro and other details I'm not aware of. I've heard appro suggestions of creating several variants of the OpenSSL libraries that appro would be used in parallell with the different MSVC

Sureware engine / PKCS#11 engine

2004-01-26 Thread Giovanni Calzuola
I am developing a software which will make use of the AEP Sureware KeyPer. I don't have one for testing pusrposes, but I know that the AEP Sureware KeyPer has a PKCS#11 interface, so what I am doing now is developing my software using the PKCS#11 engine, testing it with a smartcard. I've seen that

Re: Sureware engine / PKCS#11 engine

2004-01-26 Thread Giovanni Calzuola
Sorry, I've written to the wrong mailing-list __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager

Re: Windows DLL naming inconsistency

2004-01-26 Thread Andy Polyakov
appro and other details I'm not aware of. I've heard appro suggestions of creating several variants of the OpenSSL libraries that appro would be used in parallell with the different MSVC libraries, and appro that's where a naming convention is becoming even more important. appro appro

Re: Windows DLL naming inconsistency

2004-01-26 Thread Dr. Stephen Henson
On Mon, Jan 26, 2004, Andy Polyakov wrote: appro and other details I'm not aware of. I've heard appro suggestions of creating several variants of the OpenSSL libraries that appro would be used in parallell with the different MSVC libraries, and appro that's where a naming convention

x509_verify_cert and revocation checking

2004-01-26 Thread Amar Desai
Just for curiosity, why openssl checks revocation status of the certificate before checking whether it has expired or not? E.g. if one certificate in a certificate chain has expired then X509_verify_cert should fail (which it actually does), but before failing it checks the revocation status.

Re: Windows DLL naming inconsistency

2004-01-26 Thread Jeffrey Altman
We have the following variables which we want to express in the name of the dll: 1. run-time library [compiler x threading x debugging] Compilers: cygwin versions msvc 6.0 msvs .net msvs .net 2003 others? Threading;

Re: Windows DLL naming inconsistency

2004-01-26 Thread Jeffrey Altman
Andy Polyakov wrote: That would be great, so how does one do that? Note that I didn't say it would be trivial, nor that I know exactly how to actually do it:-) I merely said that having observed how system components [e.g. KERNEL32] are linked there seem to be a way to achieve this [noble]

Re: Windows DLL naming inconsistency

2004-01-26 Thread Jeffrey Altman
Dr. Stephen Henson wrote: That I believe is the main problem: all the runtime library dependencies which directly or indirectly call incompatible library functions. There was an attempt to fix this back in SSLeay where the application called one function which passed pointers to the malloc

Re: Windows DLL naming inconsistency

2004-01-26 Thread Andy Polyakov
That would be great, so how does one do that? Note that I didn't say it would be trivial, nor that I know exactly how to actually do it:-) I merely said that having observed how system components [e.g. KERNEL32] are linked there seem to be a way to achieve this [noble] goal. Step in the

Re: Windows DLL naming inconsistency

2004-01-26 Thread Andy Polyakov
But note that there *are* system DLL which are linked with MSVCRT.DLL. E.g. CRYPT32.DLL imports string functions and malloc/free, while WS32_32.DLL imports fopen, fclose, fgets and some string functions... Consider following dll.c snippet: #include stdio.h #ifdef ME_DLL __declspec(dllexport)

Compile SnapShot - S_IFBLK

2004-01-26 Thread ph-bgt
Hi, When I try to compile openssl-0.9.7-stable-SNAP-20040126,S_IFBLK (randfile.c) is not defined under windows. Thanks. __ OpenSSL Project http://www.openssl.org Development Mailing List

Re: Windows DLL naming inconsistency

2004-01-26 Thread Jeffrey Altman
Andy Polyakov wrote: That's why I wrote that it might be hard to accept, because it's really the last thing we want to do, implement own run-time environment, isn't it? But note that there *are* system DLL which are linked with MSVCRT.DLL. E.g. CRYPT32.DLL imports string functions and

Re: Compile SnapShot - S_IFBLK

2004-01-26 Thread Richard Levitte - VMS Whacker
In message [EMAIL PROTECTED] on Mon, 26 Jan 2004 22:17:45 +0100, ph-bgt [EMAIL PROTECTED] said: philippe.bougeret When I try to compile philippe.bougeret openssl-0.9.7-stable-SNAP-20040126, S_IFBLK philippe.bougeret (randfile.c) is not defined under windows. Thanks, I just fixed it (I hope

Re: chain of certificate

2004-01-26 Thread dhiva
You should be able to create a certificate with all these DNS listed as subjectAltName Extension. But none of the web browser (i guess openssl as well)don't know how to handle this extension. I believe RFC 2459 section 4.2.1.7. Probably you should file this as a bug(with all the browser vendor