Andy, Good point, thanks. I had to check closely too.
Why I don't want 0.9.8e is because there is a little flaw which is alrady fixed in the HEAD but still not officially released :) You know that EVP_CIPHER_CTX_key_length in this version returns ctx->cipher->key_len instead of ctx->key_len and it makes it impossible for my application to work with required ciphers. So it requires more patches in my building scripts. Also I don't want the way of communication 0.9.8 requires from applications under win32. I'd prefer to have a way to turn that part off in compiletime without patching the sources. Why? Because my 1st win32 application is not written in C and does not use msvcrt at all (so it's used solely by openssl). My 2nd application is written in C but it's a dll, while the exe (the application) is not mine and it has no relation to ssl at all and does not export anything. You see, this all makes it hard to use 0.9.8 for me. Regards, Dmitri. ----- Original Message ----- From: "Andy Polyakov via RT" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[email protected]> Sent: Monday, September 24, 2007 9:58 PM Subject: Re: [openssl.org #1555] problems under openbsd > There is no problem with C compiler and tools around it under OpenBSD > except > assembler. It's assember adds undescores to all the public symbols in the > object files No. It's not assembler that adds underscores, but OpenSSL modules that are generated with underscores for OpenBSD-i386 target. > Output of config -t is below: > Operating system: i386-whatever-openbsd > Configuring for OpenBSD-i386 > /usr/bin/perl ./Configure OpenBSD-i386 386 I should have read the report more closely as the question was about 0.9.7, while my comment referred to 0.9.8 and later [where we have unified *BSD configurations]. There is no proper support for newer versions of OpenBSD in 0.9.7. But 0.9.7 should be included in base OpenBSD dist, so you don't have to compile it yourself. If you want to compile OpenSSL, why not 0.9.8? But if it has to be 0.9.7 and has to be compiled on-site, then configuring for FreeBSD-elf instead of OpenBSD-i386 should do the trick. A. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [EMAIL PROTECTED]
