Re: [openssl.org #989] DJGPP patches for 0.9.8 and 0.9.7

2005-01-13 Thread Andy Polyakov
./Configure no-threads --prefix=/dev/env/DJDIR DJGPP Just occured to me. What if end-user system doesn't have /dev catalog on the current drive? Would an application succeed to open /dev/urandom$ even then? In other words wouldn't it more appropriate to check upon urandom$ without *any* prefix

Re: [openssl.org #1000] OpenSSL 0.9.7e fails RIPEMD160 on Sparc64

2005-01-13 Thread Gert Doering via RT
Hi, On Thu, Jan 13, 2005 at 12:09:42AM +0100, Andy Polyakov via RT wrote: Anything I should try? INSTALL is specfic about this. Try removing any compiler optimization flags... This very issue was discussed couple of times already (google for error message) in Solaris context. The error

[openssl.org #1001] potential problem with no-asm option

2005-01-13 Thread Jeff Nathan via RT
__ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]

[openssl.org #1002] Problem with mingw build of 0.9.8

2005-01-13 Thread [EMAIL PROTECTED] via RT
I have now built the snapshot from 20050105 for mingw. The 0.9.7 stable code builds and tests fine, with or without FIPS. The 0.9.8 code, however, fails the test suite at the end of test_ssl. The same error occurs when built with or without the assembler code. I am not sure where to go with this.

ENGINE issues

2005-01-13 Thread Massimiliano Pala
Dear list, I have a problem when integrating my application with LunaSA/LunaCA3 by using the ENGINE extension with our OpenCA-OCSP daemon. I successfully can execute PRE and POST commands by using `ENGINE_ctrl_cmd_string()' (e.g. CONF_PATH and login commands). The problem is that, by using

RE: ENGINE issues

2005-01-13 Thread David C. Partridge
IIRC the Luna CA3 is FIPS140-2 LEVEL 3 which means it won't allow you under nay circumstances to extract the private key from the device (non-extractable, sensitive in PKCS#11 parlance). What this means is that you need to send the data to the device to be signed (don't know how to do this using

Re: ENGINE issues

2005-01-13 Thread Massimiliano Pala
On Thu, 13 Jan 2005 12:27:57 - David C. Partridge [EMAIL PROTECTED] wrote: IIRC the Luna CA3 is FIPS140-2 LEVEL 3 which means it won't allow you under nay circumstances to extract the private key from the device (non-extractable, sensitive in PKCS#11 parlance). What this means is that you

Re: [openssl.org #989] DJGPP patches for 0.9.8 and 0.9.7

2005-01-13 Thread Doug Kaufman
On Thu, 13 Jan 2005, Andy Polyakov wrote: ./Configure no-threads --prefix=/dev/env/DJDIR DJGPP Just occured to me. What if end-user system doesn't have /dev catalog on the current drive? Would an application succeed to open /dev/urandom$ even then? In other words wouldn't it more

Re: [openssl.org #998] /dev/random and Solaris 10

2005-01-13 Thread Andy Polyakov
/dev/random is a symlink on Solaris and Solaris 10 has added O_NOFOLLOW to /usr/include/sys/fcntl.h. This causes a problem in crypto/rand/rand_unix.c where /dev/random doesn't get used, when it actually should... This is with openssl-0.9.7e and Solaris x86 10_b72. Or is it used to avoid using

Re: OS/2 support

2005-01-13 Thread Andy Polyakov
tmp_dll\o_str.obj(o_str.obj) : error L2029: 'strncasecmp' : unresolved external tmp_dll\o_str.obj(o_str.obj) : error L2029: 'strcasecmp' : unresolved external My reasoning was following. Snapshot version of o_str.c was recently modified to include e_os.h, which in turn conditionally defines

Re: [openssl.org #1000] OpenSSL 0.9.7e fails RIPEMD160 on Sparc64

2005-01-13 Thread Andy Polyakov via RT
Anything I should try? INSTALL is specfic about this. Try removing any compiler optimization flags... This very issue was discussed couple of times already (google for error message) in Solaris context. The error is believed to be a GCC 64-bit specific bug and nobody managed to prove

Fwd: RE : ENGINE issues

2005-01-13 Thread Massimiliano Pala
--- the forwarded message follows --- ---BeginMessage--- On Thu, 13 Jan 2005 16:26:33 +0100 Frédéric Donnat [EMAIL PROTECTED] wrote: Hi Massimo, Hi, As far as I know it you must LOAD (pre command I think) the ENGINE to correctly set all ENGINE function pointers... And thus initialize

Re: ENGINE issues

2005-01-13 Thread Dr. Stephen Henson
On Thu, Jan 13, 2005, Massimiliano Pala wrote: On Thu, 13 Jan 2005 12:27:57 - David C. Partridge [EMAIL PROTECTED] wrote: I just taken as an example the code from openssl, but there is something I am doing wrong somewhere... All I want to do is to enable ENGINE so all crypto

Re: [openssl.org #1000] OpenSSL 0.9.7e fails RIPEMD160 on Sparc64

2005-01-13 Thread Gert Doering via RT
Hi, On Thu, Jan 13, 2005 at 04:56:58PM +0100, Andy Polyakov via RT wrote: So indeed, this seems to be a gcc (3.3.3) optimization error.Is there a way to make OpenSSL auto-disable -O3 for specific crypto/... modules if its known that they fail on specific platforms? No. BTW, if it

RE: [openssl.org #1000] OpenSSL 0.9.7e fails RIPEMD160 on Sparc64

2005-01-13 Thread Ted Mittelstaedt
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Gert Doering via RT Sent: Thursday, January 13, 2005 12:50 AM Cc: openssl-dev@openssl.org Subject: Re: [openssl.org #1000] OpenSSL 0.9.7e fails RIPEMD160 on Sparc64 Hi, On Thu, Jan 13, 2005 at