Re: Windows DLL naming inconsistency

[Martin Germann]

Jeffrey Altman wrote:

> Why do you believe that stunnel represents the most widely used naming?

I just thougt that gcc represents the most widely used naming.

> There are widely deployed applications from
>
>IBM (ships as part of the Access IBM service)
>Time Warner's Road Runner
>The Kermit Project (Kermit 95)
>   
> and many others who distribute ssleay32.dll and libeay32.dll.

OK, but what about modifying the gcc Makefile so that it builds
ssleay32.dll and libeay32.dll?

Regards, Martin
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [CVS] OpenSSL: OpenSSL_0_9_7-stable: openssl/ Configure configopenssl...

[Richard Levitte - VMS Whacker]

In message <[EMAIL PROTECTED]> on Wed, 21 Jan 2004 14:40:07 +0100, Andy Polyakov 
<[EMAIL PROTECTED]> said:

appro> > You're not forgetting to apply this to HEAD, I hope...
appro> 
appro> Well, gcc detection and hpux64-parisc2-gcc line were in HEAD since
appro> November. Then as I mentioned in 772 ticket, HPUX64 gcc build is totally
appro> broken in HEAD. I first figure out what's wrong and *then* commit
appro> remaining bits.

OK.  Thanks, and sorry for bothering you.

-
Please consider sponsoring my work on free software.
See http://www.free.lp.se/sponsoring.html for details.
You don't have to be rich, a $10 donation is appreciated!

-- 
Richard Levitte   \ Tunnlandsvägen 3  \ [EMAIL PROTECTED]
[EMAIL PROTECTED]  \ S-168 36  BROMMA  \ T: +46-8-26 52 47
\  SWEDEN   \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis-- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/

Unsolicited commercial email is subject to an archival fee of $400.
See  for more info.

__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

[openssl.org #815] 0.9.7c wont build -mcpu=k6 is a bad value

[via RT]

Fails On
version: openssl 0.9.7c 
 openssl-0.9.7-stable-SNAP-20040121


Platform: Cobalt RaQ3 (a RedHat derivative) 
  Kernel 2.2.16C27_III on an i586

other:  gcc version egcs-2.91.66
perl 5.005_03

I have tried it "out-of-the-box" == no flags
and also with various settings.  I always get the same result.
it complains that k6 is a bad value for the cpu type, even when I tell 
it 386.

Note: This error does not occur on  0.9.6l  (but I do get a different 
unrelated? error)


[t [EMAIL PROTECTED] openssl-0.9.7c]$config 386 no-asm
Operating system: i586-whatever-linux2
Configuring for linux-k6
Configuring for linux-k6
IsWindows=0
CC=gcc
CFLAG =-DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -
DHAVE_DLFCN_H -DOPENSSL_NO_KRB5 -DOPENSSL_NO_ASM -DL_ENDIAN -DTERMIO -
O3 -fomit-frame-pointer -mcpu=k6 -Wall


[t [EMAIL PROTECTED] openssl-0.9.7c]$make
making all in crypto...


gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -
DHAVE_DLFCN_H -DOPENSSL_NO_KRB5 -DOPENSSL_NO_ASM -DL_ENDIAN -DTERMIO -
O3 -fomit-frame-pointer -mcpu=k6 -Wall   -c cryptlib.c -o cryptlib.o
cc1: bad value (k6) for -mcpu= switch
make[1]: *** [cryptlib.o] Error 1

__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [CVS] OpenSSL: OpenSSL_0_9_7-stable: openssl/ Configure configopenssl...

[Andy Polyakov]

> You're not forgetting to apply this to HEAD, I hope...

Well, gcc detection and hpux64-parisc2-gcc line were in HEAD since
November. Then as I mentioned in 772 ticket, HPUX64 gcc build is totally
broken in HEAD. I first figure out what's wrong and *then* commit
remaining bits. A.
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [CVS] OpenSSL: OpenSSL_0_9_7-stable: openssl/ Configure config openssl...

[Richard Levitte - VMS Whacker]

You're not forgetting to apply this to HEAD, I hope...

In message <[EMAIL PROTECTED]> on Wed, 21 Jan 2004 10:58:20 +0100 (CET), "Andy 
Polyakov" <[EMAIL PROTECTED]> said:

appro>   OpenSSL CVS Repository
appro>   http://cvs.openssl.org/
appro>   
appro> 
appro>   Server: cvs.openssl.org  Name:   Andy Polyakov
appro>   Root:   /e/openssl/cvs   Email:  [EMAIL PROTECTED]
appro>   Module: openssl  Date:   21-Jan-2004 10:58:19
appro>   Branch: OpenSSL_0_9_7-stable Handle: 2004012109581701
appro> 
appro>   Modified files:   (Branch: OpenSSL_0_9_7-stable)
appro> openssl Configure config
appro> openssl/crypto/bn   Makefile.ssl
appro> 
appro>   Log:
appro> Proper support for HP-UX64 gcc build.
appro> PR: 772
appro> 
appro>   Summary:
appro> RevisionChanges Path
appro> 1.314.2.89  +1  -0  openssl/Configure
appro> 1.95.2.27   +7  -6  openssl/config
appro> 1.65.2.7+3  -0  openssl/crypto/bn/Makefile.ssl
appro>   
appro> 
appro>   patch -p0 <<'@@ .'
appro>   Index: openssl/Configure
appro>   
appro>   $ cvs diff -u -r1.314.2.88 -r1.314.2.89 Configure
appro>   --- openssl/Configure  28 Sep 2003 14:07:01 -  1.314.2.88
appro>   +++ openssl/Configure  21 Jan 2004 09:58:17 -  1.314.2.89
appro>   @@ -260,6 +260,7 @@
appro># 64bit PARISC for GCC without optimization, which seems to make problems.
appro># Submitted by <[EMAIL PROTECTED]>
appro>"hpux64-parisc-gcc","gcc:-DB_ENDIAN 
-DMD32_XARRAY::-D_REENTRANT::-ldl:SIXTY_FOUR_BIT_LONG MD2_CHAR RC4_INDEX RC4_CHAR 
DES_UNROLL DES_RISC1 
DES_INT::dlfcn:hpux64-shared:-fpic::.sl.\$(SHLIB_MAJOR).\$(SHLIB_MINOR)",
appro>   +"hpux64-parisc2-gcc","gcc:-O3 -DB_ENDIAN 
-DMD32_XARRAY::-D_REENTRANT::-ldl:SIXTY_FOUR_BIT_LONG MD2_CHAR RC4_INDEX RC4_CHAR 
DES_UNROLL DES_RISC1 
DES_INT:asm/pa-risc2W.o:dlfcn:hpux64-shared:-fpic::.sl.\$(SHLIB_MAJOR).\$(SHLIB_MINOR)",
appro>
appro># IA-64 targets
appro>"hpux-ia64-cc","cc:-Ae +DD32 +O3 +Olit=all -z 
-DB_ENDIAN::-D_REENTRANT::-ldl:SIXTY_FOUR_BIT MD2_CHAR RC4_INDEX RC4_CHAR DES_UNROLL 
DES_RISC1 
DES_INT:asm/ia64-cpp.o:dlfcn:hpux-shared:+Z::.sl.\$(SHLIB_MAJOR).\$(SHLIB_MINOR)",
appro>   @@ .
appro>   patch -p0 <<'@@ .'
appro>   Index: openssl/config
appro>   
appro>   $ cvs diff -u -r1.95.2.26 -r1.95.2.27 config
appro>   --- openssl/config 20 Mar 2003 11:44:31 -  1.95.2.26
appro>   +++ openssl/config 21 Jan 2004 09:58:17 -  1.95.2.27
appro>   @@ -134,7 +134,7 @@
appro>  HPUXVER=`echo ${RELEASE}|sed -e 's/[^.]*.[0B]*//'`
appro>  case "$HPUXVER" in
appro>  1[0-9].*)   # HPUX 10 and 11 targets are unified
appro>   -  echo "${MACHINE}-hp-hpux10"; exit 0
appro>   +  echo "${MACHINE}-hp-hpux1x"; exit 0
appro>  ;;
appro>  *)
appro>  echo "${MACHINE}-hp-hpux"; exit 0
appro>   @@ -410,9 +410,10 @@
appro>  GCC_BITS="32"
appro>  if [ $GCCVER -ge 30 ]; then
appro># PA64 support only came in with gcc 3.0.x.
appro>   -# We look for the preprocessor symbol __LP64__ indicating
appro>   -# 64bit bit long and pointer.  sizeof(int) == 32 on HPUX64.
appro>   -if gcc -v -E -x c /dev/null 2>&1 | grep __LP64__ > /dev/null; then
appro>   +# We check if the preprocessor symbol __LP64__ is defined...
appro>   +if echo "__LP64__" | gcc -v -E -x c - 2>/dev/null | grep "^__LP64__" 
2>&1 > /dev/null; then
appro>   +  : # __LP64__ has slipped through, it therefore is not defined
appro>   +else
appro>  GCC_BITS="64"
appro>fi
appro>  fi
appro>   @@ -685,7 +686,7 @@
appro>  if [ $CC = "gcc" ];
appro>  then
appro>if [ $GCC_BITS = "64" ]; then
appro>   -  OUT="hpux64-parisc-gcc"
appro>   +  OUT="hpux64-parisc2-gcc"
appro>else
appro>  OUT="hpux-parisc-gcc"
appro>fi
appro>   @@ -700,7 +701,7 @@
appro>  if   [ $CPU_VERSION -ge 768 ]; then # IA-64 CPU
appro>   echo "WARNING! 64-bit ABI is the default configured ABI on 
HP-UXi."
appro>   echo " If you wish to build 32-bit library, the you have 
to"
appro>   -   echo " invoke './Configure hpux-ia32-cc' *manually*."
appro>   +   echo " invoke './Configure hpux-ia64-cc' *manually*."
appro>   if [ "$TEST" = "false" ]; then
appro>  echo " You have about 5 seconds to press Ctrl-C to 
abort."
appro>  (stty -icanon min 0 time 50; read waste) < /dev/tty
ap

Re: SSLeay compatibale

[Dr. Stephen Henson]

On Wed, Jan 21, 2004, S.Mehdi Sheikhalishahi wrote:

> Hi All
>  What's the equivalent function for PEM_read_PUBKEY in
> SSLeay?
> I want to read a public key but I cannot read It by
>  rsa = PEM_read_RSAPublicKey(fkeyfile, 0 ,0);
> function .The rsa is NULL.

There isn't an equivalent: it's OpenSSL only.

You can however use PEM_write_RSAPublicKey() on OpenSSL and
PEM_read_RSAPublicKey() on SSLeay.

Use of SSLeay however is strongly discouraged: it hasn't been maintained for
some years and has lots of unpatched (and well known) security
vilnerabilities.

Steve.
--
Dr Stephen N. Henson. Email, S/MIME and PGP keys: see homepage
OpenSSL project core developer and freelance consultant.
Funding needed! Details on homepage.
Homepage: http://www.drh-consultancy.demon.co.uk
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

SSLeay compatibale

[S.Mehdi Sheikhalishahi]

Hi All
 What's the equivalent function for PEM_read_PUBKEY in
SSLeay?
I want to read a public key but I cannot read It by
 rsa = PEM_read_RSAPublicKey(fkeyfile, 0 ,0);
function .The rsa is NULL.
HELP WAA
Thanks.

__
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [openssl.org #772] 32/64-bit detection on HPUX 11.11 with GCC

[Andy Polyakov via RT]

> Fix addressing this problem is in HEAD branch now. Please download
> ftp://ftp.openssl.org/snapshot/openssl-SNAP-20031121.tar.gz as it
> becomes available and verify if ./config works as expected.

Requestor has never reported back. Probably because hpux64 build is
severily broken in HEAD and it's virutally impossible to verify
snapshot.

> Secondly. The snapshot in question adds new target, namely
> hpux64-parisc2-gcc [with assembler support and optimizaton].
> Could you be so kind to verify it by manually invoking
> './Configure hpux64-parisc-gcc' and then running 'make; make test'?
> 
> Once everything verifies, we put it into 0.9.7 branch. A.

It's in 0.9.7 branch now. Even though it's verified, do download
ftp://ftp.openssl.org/snapshot/openssl-0.9.7-stable-SNAP-20040122.tar.gz
as it becomes available and double-check that it works. Note that it
requires /usr/ccs/bin/as to build the assembler module. If you don't
have vendor assembler, configure with no-asm option. A.

__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: Windows DLL naming inconsistency

[Jeffrey Altman]

Why do you believe that stunnel represents the most widely used naming?
There are widely deployed applications from
  IBM (ships as part of the Access IBM service)
  Time Warner's Road Runner
  The Kermit Project (Kermit 95)
 
and many others who distribute ssleay32.dll and libeay32.dll.  If anything
I would argue that the naming convention needs to be modified to include
the version number so as to prevent conflicts between 0.9.5, 0.9.6, 0.9.7,
and 0.9.8 all of which have incompatible ABIs.

Jeffrey Altman

Martin Germann wrote:

Hi,

I noticed an inconsistency in the windows library names: 

When compiling OpenSSL on windows with gcc (MinGW), the resulting ssl 
library is called 'libssl32.dll'. Using MS Visual C++ (and Borland C++, i 
suppose), the resulting binary will be called 'ssleay32.dll'.

This may cause a lot of confusion for users compiling OpenSSL on Win32. 
Therefore, I suggest to modify the targets for Visual C++ and Borland C++ 
to also build 'libssl32.dll', as this target name seems to be most widely 
used (e.g. stunnel).

Regards, Martin
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]


smime.p7s
Description: S/MIME Cryptographic Signature