"Unknown SSL protocol" when accessing server from AIX host

2010-12-03 Thread Alona Rossen
Hello, 

 

We use openssl with libcurl to programmatically access, upload to and
download from various URL's using https, ftps, and smtps protocols. We
can successfully perform our tasks on  UNIX/Linux and Windows boxes,
including Solaris on SPARC and Intel, Linux, etc. However, we
consistently receive the following type of error message when we attempt
to access SSL URL from our AIX5.3 and AIX6.1 boxes:

 

 

INFO_TEXT: 

SSLv3, TLS handshake, Client hello (1):

 

INFO_TEXT: 

Unknown SSL protocol error in connection to smtp.gmail.com:587 

 

The message is being formatted by libcurl. We use OpenSSL 0.9.8e and
0.9.8p.

We have verified that correct installation of OpenSSL is being used.

 

Please advise.

 

Thank you, 

Alona

 



"Unknown SSL protocol" when accessing server from AIX host

2010-12-03 Thread Alona Rossen
Hello, 

We use openssl with libcurl to programmatically access, upload to and download 
from various URL's using https, ftps, and smtps protocols. We can successfully 
perform our tasks on  UNIX/Linux and Windows boxes, including Solaris on SPARC 
and Intel, Linux, etc. However, we consistently receive the following type of 
error message when we attempt to access SSL URL from our AIX5.3 and AIX6.1 
boxes:


INFO_TEXT: 
SSLv3, TLS handshake, Client hello (1):

INFO_TEXT: 
Unknown SSL protocol error in connection to smtp.gmail.com:587 

The message is being formatted by libcurl. We use OpenSSL 0.9.8e and 0.9.8p.
We have verified that correct installation of OpenSSL is being used.

Please advise.

Thank you, 
Alona




Alona Rossen 
Software Developer
Connectivity Solutions Group

Open Text Corporation
 

38 Leek Crescent, Richmond Hill, ON, L4B 4N8, Canada





Phone:
 
+1 (905) 762 6001 ext. 6908
Email:

aros...@opentext.com
Web site:

http://connectivity.opentext.com















This email is protected by domestic and international copyright laws and 
treaties and is the property of Open Text Corporation, it may contain 
confidential and/or trade secret information of the Open Text Corporation 
and/or its subsidiaries (OTC), and may be subject to legal privilege in favor 
of OTC. This email may only be lawfully received, accessed, displayed on a 
computer screen, printed, copied, and/or used by the specific addressee(s) 
named above ("Authorized Recipient") for the purpose for which it was sent by 
OTC. All other rights and licenses to this email are fully reserved to OTC. If 
you are not an Authorized Recipient, you are required to immediately delete 
this email in its entirety without printing, copying, using, and/or 
re-transmitting this email, either in whole or in part. The transmission of 
this email by OTC is not to be construed as a waiver by OTC and/or the 
individual sending this email on behalf of OTC of any of their respective 
rights or privileges at law or otherwise, howsoever arising.


__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-users@openssl.org
Automated List Manager   majord...@openssl.org


multithreaded application crashes on windows

2011-03-16 Thread Alona Rossen
 

OpenSSL 0.9.8e

Application crashes in multithreaded environment on Windows.

We use libcurl with OpenSSL and execute HTTP(S) POST/GET. When the
application involves SSL (HTTPS), it crashes in MT environment. The same
execution flow is successful if SSL is not involved (HTTP).

 

Please advise if there is a know workaround for this issue.

 

 

Thank you, 

Alona



building OpenSSL on AIX53/AIX61

2011-03-21 Thread Alona Rossen
Hi All, 

 

I built OpenSSL 0.9.8e and OpenSSL 1.0.0d on AIX 53 and AIX61. I
configured using the following Configure options:

 

 

Configure aix-cc shared

 

In the result, numerous symbols are not being exported:

 

exec(): 0509-036 Cannot load program ./GenExec because of the following
errors:

rtld: 0712-001 Symbol CRYPTO_num_locks was referenced

  from module /home/PreTest/App/libGenSys.so(), but a runtime
definition

  of the symbol was not found.

rtld: 0712-001 Symbol CRYPTO_malloc was referenced

  from module /home/PreTest/App/libGenSys.so(), but a runtime
definition

  of the symbol was not found.

rtld: 0712-001 Symbol CRYPTO_set_locking_callback was referenced

  from module /home/PreTest/App/libGenSys.so(), but a runtime
definition

  of the symbol was not found.

 

Please advise. 

 

Thank you, 

Alona

 



Alona Rossen 

Software Developer

Connectivity Solutions Group

  <http://www.opentext.com/2/email-signature-logo> 
Open Text Corporation

 

  <http://www.opentext.com/2/email-signature-event> 

38 Leek Crescent, Richmond Hill, ON, L4B 4N8, Canada

 

Phone:

 

+1 (905) 762 6001 ext. 6908

Email:

aros...@opentext.com <mailto:volodymyr.zabolot...@opentext.com> 

Web site:

http://connectivity.opentext.com <http://connectivity.opentext.com> 

 

 

 

 

 

 

 

 

 

 

 

This email is protected by domestic and international copyright laws and
treaties and is the property of Open Text Corporation, it may contain
confidential and/or trade secret information of the Open Text
Corporation and/or its subsidiaries (OTC), and may be subject to legal
privilege in favor of OTC. This email may only be lawfully received,
accessed, displayed on a computer screen, printed, copied, and/or used
by the specific addressee(s) named above ("Authorized Recipient") for
the purpose for which it was sent by OTC. All other rights and licenses
to this email are fully reserved to OTC. If you are not an Authorized
Recipient, you are required to immediately delete this email in its
entirety without printing, copying, using, and/or re-transmitting this
email, either in whole or in part. The transmission of this email by OTC
is not to be construed as a waiver by OTC and/or the individual sending
this email on behalf of OTC of any of their respective rights or
privileges at law or otherwise, howsoever arising.

 

 

<><>

cryptographic algorithms

2011-05-05 Thread Alona Rossen
 

Hello, 

 

Please list all encryption algorithms supported by OpenSSL 0.9.8e,
0.9.8m and 1.0.0d.

It looks like that http://www.openssl.org/docs/crypto/crypto.html has
not been updated for a while and does not list ECC and possibly some
other algorithms.

 

 

Thank you, 

Alona



building OpenSSL 0.9.8/1.0.0 on Solarisx86

2010-04-23 Thread Alona Rossen
 

Hello, 

 

I built 32-bit OpenSSL 0.9.8 and OpenSSL 1.0.0 on Solaris10x86_64
(64-bit kernel on Intel) with gcc compiler. Makefiles were generated
with the following command: 

 

"Configure solaris-x86-gcc"

 

Test executables provided with OpenSSL and other executables and
libraries linked to libcrypto.* and libssl.* statically or dynamically
dump core in init:

 

core 'core' of 4479:./exec

 fd28f5c5 _init(feffb28c, feffdd58, feffb818, fc280c90, fdfc01ac,
fd28f5b0) + 15

 fefd4c11 call_init (fc280c50, 1) + f5

 fefd4194 setup(8047b08, 8047b88, 0, 8047fed, 1000, fefc9141) + fd4

 fefe005e _setup   (8047abc, feffbaec, 3, 8047b00, 4, 8047b08) + 2ba

 fefcaa1c _rt_boot (0, 8047bfa, 8047c06, 8047c49, 8047c56, 8047c5d) + 56
08047bf0  ()

 

And probably is happened when calling init of curl library:

 

04487: 1: calling .init (done):
/export/home/PreTest/genio/libGShricudata.so.34

04487: 1:

04487: 1: calling .init (from sorted order): /usr/lib/libz.so.1

04487: 1:

04487: 1: calling .init (done): /usr/lib/libz.so.1

04487: 1:

04487: 1: calling .init (from sorted order):
/export/home/PreTest/genio/libcurl.so.4

04487: 1:

Segmentation Fault(coredump)

 

libcurl.so.4 is statically linked to libcrypto and libssl.

 

Core dump does not occur with 64-bit libcrypto.* and libssl.*.

We were able to create usable 32- and 64-bit libraries on 64-bit kernel
using platform specific compilers on Solaris SPARC, AIX, HP-UX.

 

This is our system info:

SunOS viola 5.10 Generic_141445-09 i86pc i386 i86pc

 

/export/home/sambuild/OpenSSL> more /etc/release

   Solaris 10 10/09 s10x_u8wos_08a X86

   Copyright 2009 Sun Microsystems, Inc.  All Rights Reserved.

Use is subject to license terms.

   Assembled 16 September 2009

/export/home/sambuild/OpenSSL> /usr/bin/isainfo -kv

64-bit amd64 kernel modules

 

Please advise. 

 

Thank you, 

Alona

Alona Rossen 
Software developer 
Connectivity Solutions Group 
Open Text 
Phone: +1 (905) 762-6001 ext. 6908 
aros...@opentext.com <http://www.hummingbird.com/>  

 



RE: building OpenSSL 0.9.8/1.0.0 on Solarisx86

2010-04-23 Thread Alona Rossen
Specifyng solaris64-x86_64-gcc as a target results in a 64-bit library,
while we need a 32-bit library.

-Original Message-
From: owner-openssl-us...@openssl.org
[mailto:owner-openssl-us...@openssl.org] On Behalf Of Dr. David Kirkby
Sent: April 23, 2010 1:33 PM
To: openssl-users@openssl.org
Subject: Re: building OpenSSL 0.9.8/1.0.0 on Solarisx86

Alona Rossen wrote:
>  
> 
> Hello,
> 
>  
> 
> I built 32-bit OpenSSL 0.9.8 and OpenSSL 1.0.0 on Solaris10x86_64 
> (64-bit kernel on Intel) with gcc compiler. Makefiles were generated 
> with the following command:
> 
>  
> 
> "Configure solaris-x86-gcc"

Try solaris64-x86_64-gcc as the target, which was the default when I run
Configure.

I've built 0.9.8l on a Sun Ultra 27 (quad core 3.33 GHz Xeon processor)
using 
OpenSolaris 06/2009 and gcc 4.3.4. It builds fine and passes tests

DONE via BIO pair: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024
bit RSA
DONE via BIO pair: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024
bit RSA
DONE via BIO pair: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024
bit RSA
10 handshakes of 256 bytes done
Approximate total server time:   0.05 s
Approximate total client time:   0.00 s
Test IGE mode
../util/shlib_wrap.sh ./igetest
Test JPAKE
../util/shlib_wrap.sh ./jpaketest
No JPAKE support
make[1]: Leaving directory `/export/home/drkirkby/openssl-0.9.8l/test'
util/opensslwrap.sh version -a
OpenSSL 0.9.8l 5 Nov 2009
built on: Fri Apr 23 18:24:58 BST 2010
platform: solaris64-x86_64-gcc
options:  bn(64,64) md2(int) rc4(1x,char) des(idx,cisc,16,int) idea(int)

blowfish(ptr2)
compiler: gcc -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H
-m64 -O3 
-Wall -DL_ENDIAN -DMD32_REG_T=int -DOPENSSL_BN_ASM_MONT -DSHA1_ASM
-DSHA256_ASM 
-DSHA512_ASM -DMD5_ASM -DAES_ASM
OPENSSLDIR: "/usr/local/ssl"
drkir...@hawk:~/openssl-0.9.8l$


I have not tried this on Solaris 10 though - at least not on x86. I have
built 
versions on SPARC before, but that is less relevant to you.

dave
__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-users@openssl.org
Automated List Manager   majord...@openssl.org
__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-users@openssl.org
Automated List Manager   majord...@openssl.org


RE: building OpenSSL 0.9.8/1.0.0 on Solarisx86

2010-04-23 Thread Alona Rossen
We can give an access to our system. How can we contact a developer? 

-Original Message-
From: owner-openssl-us...@openssl.org
[mailto:owner-openssl-us...@openssl.org] On Behalf Of Dr. David Kirkby
Sent: April 23, 2010 3:13 PM
To: openssl-users@openssl.org
Subject: Re: building OpenSSL 0.9.8/1.0.0 on Solarisx86

Alona Rossen wrote:
> Specifyng solaris64-x86_64-gcc as a target results in a 64-bit
library,
> while we need a 32-bit library.

Oh, sorry i missed that.

I also failed to create a 32-bit library. It so happened that in the
software I 
wanted to develop, 64-bit was more sensible, so I ignored the fact I was
unable 
to create a 32-bit library.

I believe you are correct in saying this will not work. You will
probably need 
the assistance of a developer in that case. It might be easier if you
can give 
them access to a Solaris system, though with VirtualBox, they should be
able to 
set one up easily.

dave

> 
> -Original Message-
> From: owner-openssl-us...@openssl.org
> [mailto:owner-openssl-us...@openssl.org] On Behalf Of Dr. David Kirkby
> Sent: April 23, 2010 1:33 PM
> To: openssl-users@openssl.org
> Subject: Re: building OpenSSL 0.9.8/1.0.0 on Solarisx86
> 
> Alona Rossen wrote:
>>  
>>
>> Hello,
>>
>>  
>>
>> I built 32-bit OpenSSL 0.9.8 and OpenSSL 1.0.0 on Solaris10x86_64 
>> (64-bit kernel on Intel) with gcc compiler. Makefiles were generated 
>> with the following command:
>>
>>  
>>
>> "Configure solaris-x86-gcc"
> 
> Try solaris64-x86_64-gcc as the target, which was the default when I
run
> Configure.
> 
> I've built 0.9.8l on a Sun Ultra 27 (quad core 3.33 GHz Xeon
processor)
> using 
> OpenSolaris 06/2009 and gcc 4.3.4. It builds fine and passes tests
> 
> DONE via BIO pair: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024
> bit RSA
> DONE via BIO pair: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024
> bit RSA
> DONE via BIO pair: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024
> bit RSA
> 10 handshakes of 256 bytes done
> Approximate total server time:   0.05 s
> Approximate total client time:   0.00 s
> Test IGE mode
> ../util/shlib_wrap.sh ./igetest
> Test JPAKE
> ../util/shlib_wrap.sh ./jpaketest
> No JPAKE support
> make[1]: Leaving directory `/export/home/drkirkby/openssl-0.9.8l/test'
> util/opensslwrap.sh version -a
> OpenSSL 0.9.8l 5 Nov 2009
> built on: Fri Apr 23 18:24:58 BST 2010
> platform: solaris64-x86_64-gcc
> options:  bn(64,64) md2(int) rc4(1x,char) des(idx,cisc,16,int)
idea(int)
> 
> blowfish(ptr2)
> compiler: gcc -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN
-DHAVE_DLFCN_H
> -m64 -O3 
> -Wall -DL_ENDIAN -DMD32_REG_T=int -DOPENSSL_BN_ASM_MONT -DSHA1_ASM
> -DSHA256_ASM 
> -DSHA512_ASM -DMD5_ASM -DAES_ASM
> OPENSSLDIR: "/usr/local/ssl"
> drkir...@hawk:~/openssl-0.9.8l$
> 
> 
> I have not tried this on Solaris 10 though - at least not on x86. I
have
> built 
> versions on SPARC before, but that is less relevant to you.
> 
> dave
> __
> OpenSSL Project http://www.openssl.org
> User Support Mailing Listopenssl-users@openssl.org
> Automated List Manager   majord...@openssl.org
> __
> OpenSSL Project http://www.openssl.org
> User Support Mailing Listopenssl-users@openssl.org
> Automated List Manager   majord...@openssl.org
> 

__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-users@openssl.org
Automated List Manager   majord...@openssl.org
__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-users@openssl.org
Automated List Manager   majord...@openssl.org


building OpenSSL 0.9.8/1.0.0 on Solarisx86

2010-04-26 Thread Alona Rossen
 

 

 

Hello, 

 

Has anyone been able to build usable libcrypto/libssl on Solarisx86 ?

 

I built 32-bit OpenSSL 0.9.8 and OpenSSL 1.0.0 on Solaris10x86_64
(64-bit kernel on Intel) with gcc compiler. Makefiles were generated
with the following command: 

 

"Configure solaris-x86-gcc"

 

Test executables provided with OpenSSL and other executables and
libraries linked to libcrypto.* and libssl.* statically or dynamically
dump core in init:

 

core 'core' of 4479:./exec

 fd28f5c5 _init(feffb28c, feffdd58, feffb818, fc280c90, fdfc01ac,
fd28f5b0) + 15

 fefd4c11 call_init (fc280c50, 1) + f5

 fefd4194 setup(8047b08, 8047b88, 0, 8047fed, 1000, fefc9141) + fd4

 fefe005e _setup   (8047abc, feffbaec, 3, 8047b00, 4, 8047b08) + 2ba

 fefcaa1c _rt_boot (0, 8047bfa, 8047c06, 8047c49, 8047c56, 8047c5d) + 56
08047bf0  ()

 

And probably is happened when calling init of curl library:

 

04487: 1: calling .init (done):
/export/home/PreTest/genio/libGShricudata.so.34

04487: 1:

04487: 1: calling .init (from sorted order): /usr/lib/libz.so.1

04487: 1:

04487: 1: calling .init (done): /usr/lib/libz.so.1

04487: 1:

04487: 1: calling .init (from sorted order):
/export/home/PreTest/genio/libcurl.so.4

04487: 1:

Segmentation Fault(coredump)

 

libcurl.so.4 is statically linked to libcrypto and libssl.

 

Core dump does not occur with 64-bit libcrypto.* and libssl.*.

We were able to create usable 32- and 64-bit libraries on 64-bit kernel
using platform specific compilers on Solaris SPARC, AIX, HP-UX.

 

This is our system info:

SunOS viola 5.10 Generic_141445-09 i86pc i386 i86pc

 

/export/home/sambuild/OpenSSL> more /etc/release

   Solaris 10 10/09 s10x_u8wos_08a X86

   Copyright 2009 Sun Microsystems, Inc.  All Rights Reserved.

Use is subject to license terms.

   Assembled 16 September 2009

/export/home/sambuild/OpenSSL> /usr/bin/isainfo -kv

64-bit amd64 kernel modules

 

/export/home/sambuild/OpenSSL > gcc -v

Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs

Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure
--prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as
--with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++
--enable-shared

Thread model: posix

gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)

 

Please advise. 

 

Thank you, 

Alona

Alona Rossen 
Software developer 
Connectivity Solutions Group 
Open Text 
Phone: +1 (905) 762-6001 ext. 6908 
aros...@opentext.com <http://www.hummingbird.com/>  

 



RE: building OpenSSL 0.9.8/1.0.0 on Solarisx86

2010-04-28 Thread Alona Rossen
In fact, we were able to create usable 32-bit with SunStudio compilers
(C++ 5.0, 5.5, 5.8) on Solaris8/9/10 on SPARC.

-Original Message-
From: owner-openssl-us...@openssl.org
[mailto:owner-openssl-us...@openssl.org] On Behalf Of Dr. David Kirkby
Sent: April 23, 2010 3:13 PM
To: openssl-users@openssl.org
Subject: Re: building OpenSSL 0.9.8/1.0.0 on Solarisx86

Alona Rossen wrote:
> Specifyng solaris64-x86_64-gcc as a target results in a 64-bit
library,
> while we need a 32-bit library.

Oh, sorry i missed that.

I also failed to create a 32-bit library. It so happened that in the
software I 
wanted to develop, 64-bit was more sensible, so I ignored the fact I was
unable 
to create a 32-bit library.

I believe you are correct in saying this will not work. You will
probably need 
the assistance of a developer in that case. It might be easier if you
can give 
them access to a Solaris system, though with VirtualBox, they should be
able to 
set one up easily.

dave

> 
> -Original Message-
> From: owner-openssl-us...@openssl.org
> [mailto:owner-openssl-us...@openssl.org] On Behalf Of Dr. David Kirkby
> Sent: April 23, 2010 1:33 PM
> To: openssl-users@openssl.org
> Subject: Re: building OpenSSL 0.9.8/1.0.0 on Solarisx86
> 
> Alona Rossen wrote:
>>  
>>
>> Hello,
>>
>>  
>>
>> I built 32-bit OpenSSL 0.9.8 and OpenSSL 1.0.0 on Solaris10x86_64 
>> (64-bit kernel on Intel) with gcc compiler. Makefiles were generated 
>> with the following command:
>>
>>  
>>
>> "Configure solaris-x86-gcc"
> 
> Try solaris64-x86_64-gcc as the target, which was the default when I
run
> Configure.
> 
> I've built 0.9.8l on a Sun Ultra 27 (quad core 3.33 GHz Xeon
processor)
> using 
> OpenSolaris 06/2009 and gcc 4.3.4. It builds fine and passes tests
> 
> DONE via BIO pair: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024
> bit RSA
> DONE via BIO pair: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024
> bit RSA
> DONE via BIO pair: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024
> bit RSA
> 10 handshakes of 256 bytes done
> Approximate total server time:   0.05 s
> Approximate total client time:   0.00 s
> Test IGE mode
> ../util/shlib_wrap.sh ./igetest
> Test JPAKE
> ../util/shlib_wrap.sh ./jpaketest
> No JPAKE support
> make[1]: Leaving directory `/export/home/drkirkby/openssl-0.9.8l/test'
> util/opensslwrap.sh version -a
> OpenSSL 0.9.8l 5 Nov 2009
> built on: Fri Apr 23 18:24:58 BST 2010
> platform: solaris64-x86_64-gcc
> options:  bn(64,64) md2(int) rc4(1x,char) des(idx,cisc,16,int)
idea(int)
> 
> blowfish(ptr2)
> compiler: gcc -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN
-DHAVE_DLFCN_H
> -m64 -O3 
> -Wall -DL_ENDIAN -DMD32_REG_T=int -DOPENSSL_BN_ASM_MONT -DSHA1_ASM
> -DSHA256_ASM 
> -DSHA512_ASM -DMD5_ASM -DAES_ASM
> OPENSSLDIR: "/usr/local/ssl"
> drkir...@hawk:~/openssl-0.9.8l$
> 
> 
> I have not tried this on Solaris 10 though - at least not on x86. I
have
> built 
> versions on SPARC before, but that is less relevant to you.
> 
> dave
> __
> OpenSSL Project http://www.openssl.org
> User Support Mailing Listopenssl-users@openssl.org
> Automated List Manager   majord...@openssl.org
> __
> OpenSSL Project http://www.openssl.org
> User Support Mailing Listopenssl-users@openssl.org
> Automated List Manager   majord...@openssl.org
> 

__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-users@openssl.org
Automated List Manager   majord...@openssl.org
__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-users@openssl.org
Automated List Manager   majord...@openssl.org


unable to build dynamic library on HP-UX RISC and Itanium

2010-06-02 Thread Alona Rossen
Hello, 

 

Building dynamic library on HP-UX fails despite I explicitly specify
'shared' as Configure argument:

 

./Configure hpux64-ia64-cc -D_REENTRANT shared

 

 

Please advise.

 

Thank you, 

Alona




 

   


 



 

 

 

 

 

 

 

 

This email is protected by domestic and international copyright laws and
treaties and is the property of Open Text Corporation, it may contain
confidential and/or trade secret information of the Open Text
Corporation and/or its subsidiaries (OTC), and may be subject to legal
privilege in favor of OTC. This email may only be lawfully received,
accessed, displayed on a computer screen, printed, copied, and/or used
by the specific addressee(s) named above ("Authorized Recipient") for
the purpose for which it was sent by OTC. All other rights and licenses
to this email are fully reserved to OTC. If you are not an Authorized
Recipient, you are required to immediately delete this email in its
entirety without printing, copying, using, and/or re-transmitting this
email, either in whole or in part. The transmission of this email by OTC
is not to be construed as a waiver by OTC and/or the individual sending
this email on behalf of OTC of any of their respective rights or
privileges at law or otherwise, howsoever arising.

 

 

<>

RE: unable to build dynamic library on HP-UX RISC and Itanium

2010-06-03 Thread Alona Rossen
This is a suggested configuration. -D stands for preprocessor "define".

/home/sambuild/OpenSSL> ./config -h
Usage: config [options]
 -d Add a debug- prefix to machine choice.
 -t Test mode, do not run the Configure perl script.
 -h This help.

Any other text will be passed to the Configure perl script.
See INSTALL for instructions.

Operating system: 9000/800-hp-hpux1x
WARNING! If you wish to build 64-bit library then you have to
 invoke './Configure hpux64-parisc2-cc' *manually*.
Configuring for hpux-parisc2-cc
/usr/bin/perl ./Configure hpux-parisc2-cc -D_REENTRANT
/home/sambuild/OpenSSL> uname -a
HP-UX rndhp11i B.11.11 U 9000/800 192242760 unlimited-user license
/home/sambuild/OpenSSL>

-Original Message-
From: William A. Rowe Jr. [mailto:wr...@rowe-clan.net] 
Sent: Wednesday, June 02, 2010 4:32 PM
To: openssl-users@openssl.org
Cc: Alona Rossen
Subject: Re: unable to build dynamic library on HP-UX RISC and Itanium

On 6/2/2010 11:08 AM, Alona Rossen wrote:
> 
> Building dynamic library on HP-UX fails despite I explicitly specify
> ‘shared’ as Configure argument:
> 
> ./Configure hpux64-ia64-cc -D_REENTRANT shared

Why are you adding -D for _REENTRANT?

I did a very similar build last week, no such problems, would you care
to be more specific about which OpenSSL package you are configuring?


RE: unable to build dynamic library on HP-UX RISC and Itanium

2010-06-03 Thread Alona Rossen
Extra -DXXX does not heart the preprocessor :-)

This OpenSSL 0.9.8


-Original Message-
From: William A. Rowe Jr. [mailto:wr...@rowe-clan.net] 
Sent: June 2, 2010 5:11 PM
To: Alona Rossen
Cc: openssl-users@openssl.org
Subject: Re: unable to build dynamic library on HP-UX RISC and Itanium

On 6/2/2010 4:04 PM, Alona Rossen wrote:
> This is a suggested configuration. -D stands for preprocessor
"define".

The reason I ask is that the entries in Configure should provide the
necessary defines, and if not, that is a bug.  As it was 'suggested',
we'll just presume things are fine w/w-o it.

You still failed to identify the openssl package you were configuring,
which doesn't give anyone much to go on, especially those who are in
some position to look at the problem.

__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-users@openssl.org
Automated List Manager   majord...@openssl.org


undef symbols on HP-UX11.11 RISC

2010-06-24 Thread Alona Rossen
Hello, 

 

I receive undef symbols when I build OpenSSL 0.9.8e or OpenSSL1.0.0a on
HP-UX11.11 RISC :

 

 

$> nm libcrypto.a | grep builtin

EC_get_builtin_curves|  1236|extern|entry  |$CODE$

ENGINE_load_builtin_engines| 0|extern|entry  |$CODE$

OPENSSL_load_builtin_modules| 0|extern|entry  |$CODE$

ENGINE_load_builtin_engines|  |undef |code   |

OPENSSL_load_builtin_modules|  |undef |code   |

 

 

./Configure hpux-parisc2-cc

 

 

 

Please advise.

 

 

Thank you, 

Alla



OpenSSL ECCN #

2012-08-20 Thread Alona Rossen
Hello,

We need OpenSSL ECCN # for our records. Please advise if this information can 
be obtained.

Thank you,
Alona Rossen