Dynamically loading openSSL dlls

2008-09-10 Thread Raymond Zhou
Hi there,   I am using axis2/c to build a web service client, and axis2/c depends on openSSL to support SSL. The way that axis2/c is currently built requires resolving all the symbols at load time, which means that the openSSL dlls have to present in the class path even if my web services does

Re: Dynamically loading openSSL dlls

2008-09-10 Thread Thomas J. Hruska
Raymond Zhou wrote: Hi there, My goal is to modify axis2/c so that I can load the openSSL dlls at runtime, this means that I will need the dlls to exist in the class path only if my web service calls require SSL communication. The AXIS2/c mainly calls the openSSL apis starting with SSL_, like

Re: openssl 0.9.8h on Solaris 10.3 amd64 blues

2008-09-10 Thread Douglas E. Engert
[EMAIL PROTECTED] wrote: Hi, I've waisted most of my day today with openssl deployment on the aforementioned server. Any help would be greatly appreciated. I compile using gcc32 with the following options: Configure solaris-x86-gcc threads no-krb5 I definitely need threads. Compilation goes

OpenSSL executable for Windows 2003 (32 bit) - Unattended Install

2008-09-10 Thread Joe Steorts
Hi, I am trying to install Win32OpenSSL-0_9_8g.exe on Windows 2003 server with an uattended install. I saw the exchange shown below at http://www.nabble.com/OpenSSL-executable-for-Windows-2003-(32-bit)-td19367245.html . I downloaded Win32OpenSSL-0_9_8g.exe and Win32OpenSSL-0_9_8h.exe from

Re: Received error 127 when installing Openssl

2008-09-10 Thread Ger Hobbelt
Doesn't sound to me like an OpenSSL error, rather a shell/makefile going pearshaped because you haven't got 'gcc' (the GNU C compiler) installed. Hence check your installed packages and make sure gcc and glibc are in the installed set. Then make also sure your account can actually use those.

Re: Dynamically loading openSSL dlls

2008-09-10 Thread Ger Hobbelt
That's funny. I only got a message containing 'I'. Hm... :-S Anyway, +1 for Thomas' answer. Did it a bit different myself one time to prevent lots of GetProcAddress blues: find out which calls/functionality you need, write a 'wrapper' DLL offering just that functionality (using your own

Re: openssl 0.9.8h on Solaris 10.3 amd64 blues

2008-09-10 Thread Douglas E. Engert
Let me correct the previous note. I had added no-asm when building the debug version. With a non-debug version and no-asm the tests work. So the problem apears to be with the asm modules. Douglas E. Engert wrote: [EMAIL PROTECTED] wrote: Hi, I've waisted most of my day today with openssl

What is left of ITS will be out of the office PM today

2008-09-10 Thread stephen . kitchener
I will be out of the office starting 10/09/2008 and will not return until 11/09/2008. IBM Deskside support will be available in Jay's Office - Unix, you have to contact HELP desk as you should be anyway :-) __ OpenSSL Project

Re: openssl 0.9.8h on Solaris 10.3 amd64 blues

2008-09-10 Thread nbalkanas
Dear Doug, Thanks a lot for the fast reply. The no-asm did it. I imagine this may have some performance penalties since it seems to use it for shared memory. On the side, os/compiler option debug-solaris-x86-gcc doesn't seem to be supported in 0.9.8h. Unfortunately the whole stack trace is

Re: The Authority Key ID extension

2008-09-10 Thread Silviu VLASCEANU
Hello, Sorry for the delay, I had some problem with... delays :). I have carefully read all of the suggestions from Kyle and Patrick. However, the serial issue was the most flagrant, definitely and I have immediately defined one. Concerning the other suggestions (KU, EKU, AKI), I agree with them

Re: openssl 0.9.8h on Solaris 10.3 amd64 blues

2008-09-10 Thread Douglas E. Engert
[EMAIL PROTECTED] wrote: Dear Doug, Thanks a lot for the fast reply. The no-asm did it. I imagine this may have some performance penalties since it seems to use it for shared memory. I also tried the fix Andy pointed out in the PROBLEMS file. http://www.openssl.org/~appro/values.c It creates

Re: openssl 0.9.8h on Solaris 10.3 amd64 blues

2008-09-10 Thread nbalkanas
Yes. I tried it myself and works. Indeed it is an incompatibility between solaris linker and solaris gcc. It is recommended not only because of performance, but because a broken gcc might affect all future compilations. I hope the guys in gcc get wind of this. Many thanks to Andy, as well.

build error vsc++express 2008 win32 openssl

2008-09-10 Thread James Owen
I tried building the sources (openssl-0.9.7m, openssl-0.9.8g, openssl-0.9.8h) with 2008 express and failed every time with the same error. cl /Fotmp32dll\cversion.obj -Iinc32 -Itmp32dll /MD /W3 /WX / Ox /O2 /Ob2 /Gs0 /GF /Gy /nologo -DOPENSSL_SYSNAME_WIN32 -DWIN32_LEAN_AND_MEAN -

Re: The Authority Key ID extension

2008-09-10 Thread Kyle Hamilton
If you're getting pronounced jitter on your client machines, I'd suggest two things: 1) install ntp clients on them, and 2) create your client certificates with a notBefore date of (now - 10m). The concept of 'time' is that there is One True Time. The problem is that the One True Time is

Re: OpenSSL executable for Windows 2003 (32 bit) - Unattended Install

2008-09-10 Thread Thomas J. Hruska
Joe Steorts wrote: Hi, I am trying to install Win32OpenSSL-0_9_8g.exe on Windows 2003 server with an uattended install. I saw the exchange shown below at http://www.nabble.com/OpenSSL-executable-for-Windows-2003-(32-bit)-td19367245.html . I downloaded Win32OpenSSL-0_9_8g.exe and

Re: [openssl-users] Re: X509 V1 version info

2008-09-10 Thread Madhusudhan reddy
Hello Experties there, could you pls help me? On Thu, Sep 4, 2008 at 3:45 PM, Kyle Hamilton [EMAIL PROTECTED] wrote: Honestly, I'm not sure. DER says that there is One True Encoding for any given certificate, and I think (but am not sure) that part of it is that optional parameters are not

RE: [openssl-users] Re: X509 V1 version info

2008-09-10 Thread David Schwartz
Hello Experties there, could you pls help me? What's the question exactly? On Thu, Sep 4, 2008 at 3:45 PM, Kyle Hamilton [EMAIL PROTECTED] wrote: Honestly, I'm not sure. DER says that there is One True Encoding for any given certificate, and I think (but am not sure) that part of it is