AW: Import private key with d2i_AutoPrivateKey

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 ... and was this version number in 0.9.7g not user or optional? It's a bit astonishing that it worked with an older but not with the current version! What standard is used to describe the private key in this method (sorry, I looked for it, but I

Re: SSL_connect and SSL_accept

Thanks for replying. I guess we are on the same page now. The only thing is that you are asking the same question that I am asking everyone on this list What scenario may cause the SSL_connect to return error to the caller, without writing a single byte on the underlying tcp connection (which

Re: SSL_connect and SSL_accept

Thanks for replying. I guess we are on the same page now. The only thing is that you are asking the same question that I am asking everyone on this list What scenario may cause the SSL_connect to return error to the caller, without writing a single byte on the underlying tcp connection (which

Re: SSL_connect and SSL_accept

snip I have spent quite some time with SSL_connect, and apart from tcp level socket failures (transient/fatal) and SSL Handshake failures it cannot return error, so ur case is NOT POSSIBLE unless the HOST has run out of memory wherein Openssl_malloc itself fails. So I dont suppose you need to

Trouble compiling and openssl 0.9.8 d or e on solari10

Hello, I'm in trouble with openlls 0.9.8 on solaris10 : I compile it either witch gcc or sun cc (studio11), and when I try an s_client command on our web server I got the following error : /opt/openssl-0.9.8e/bin/openssl s_client -host www -port 443 CONNECTED(0004) depth=1

Re: Trouble compiling and openssl 0.9.8 d or e on solari10

Frederic Goudal a écrit : I'm in trouble with openlls 0.9.8 on solaris10 : I compile it either witch gcc or sun cc (studio11), and when I try an s_client command on our web server I got the following error : Did you patch Studio 11? the original version had issues with OpenSSL when built with

Re: Trouble compiling and openssl 0.9.8 d or e on solari10

Laurent Blume [EMAIL PROTECTED] Date: Fri, 30 Mar 2007 16:39:02 +0200 Subject: Re: Trouble compiling and openssl 0.9.8 d or e on solari10 Frederic Goudal a écrit : I'm in trouble with openlls 0.9.8 on solaris10 : I compile it either witch gcc or sun cc (studio11), and when I try an s_client

Re: Trouble compiling and openssl 0.9.8 d or e on solari10

[EMAIL PROTECTED] a écrit : I don't know. Which patch ? Those are the latest for Studio 11 on Solaris x86: 120759-10 Sun Studio 11_x86: Sun Compiler Common patch for x86 backend 120762-03 Sun Studio 11_x86: Patch for Performance Analyzer Tools 121016-05 Sun Studio 11_x86: Patch for Sun C_x86

Re: Trouble compiling and openssl 0.9.8 d or e on solari10

Laurent Blume [EMAIL PROTECTED] Date: Fri, 30 Mar 2007 17:12:12 +0200 Subject: Re: Trouble compiling and openssl 0.9.8 d or e on solari10 [EMAIL PROTECTED] a écrit : I don't know. Which patch ? Those are the latest for Studio 11 on Solaris x86: 120759-10 Sun Studio 11_x86: Sun Compiler

RE: Really confusing with SSL_write

Hi, I've been trying to figure out (plus testing) how to actually use SSL_write. Call SSL_write with the same parameters until it succeeds. You need to handle WANT_READ and WANT_WRITE return values. Mark __ OpenSSL Project

RE: SSL_connect and SSL_accept

So what you are saying is the scenario we have been discussing so far is possible ONLY in case of memory allocation issues NOT OTHERWISE. I guess I will have a look at the SSL_connect code before I just trust this :-) I would still recommend coding to handle this case. Perhaps the next

Re: Really confusing with SSL_write

Hi, I've been trying to figure out (plus testing) how to actually use SSL_write. Call SSL_write with the same parameters until it succeeds. You need to handle WANT_READ and WANT_WRITE return values. I guess that is clear enough. but does that imply if I call SSL_write(ssl, buffer, len),

RE: Really confusing with SSL_write

Call SSL_write with the same parameters until it succeeds. You need to handle WANT_READ and WANT_WRITE return values. I guess that is clear enough. but does that imply if I call SSL_write(ssl, buffer, len), it will ONLY return len or 0 ? I mean if it returns len/2 (sent only half

Re: Really confusing with SSL_write

On Friday 30 March 2007 22:41, David Schwartz wrote: Call SSL_write with the same parameters until it succeeds. You need to handle WANT_READ and WANT_WRITE return values. I guess that is clear enough. but does that imply if I call SSL_write(ssl, buffer, len), it will ONLY return

RE: Really confusing with SSL_write

I see, so if I disable PARTIAL_WRITES, will that mean that it will return values as I wrote up there? PARTIAL_WRITES has no effect on the meaning of the return value. It just controls whether or not the internal write logic tries to continue writing if the underlying write partially completes.

Compilation Problem on Sun Solaris Optron 10

Hi All, I have compiled openssl on many unix flavours and it worked fine. When I try on Solaris Optron 10 machine. It gets compiled, however i see Segmentation Fault /core-dump messages. (I am compiling openssl for Cfengine as it is one of its pre-reqs) I recompiled openssl forcefully in