Re: Session not re-used when exported then re-imported.

Hi Lutz Have run with ssldump, there doesn't seem to be any session_id being sent from the client. I presume it would show up something like session_id[32]=... under the C>S Handshake section. What else might I be doing wrong, or have not set ? In overview this is what I do: --- startup cod

Re: Session not re-used when exported then re-imported.

On Thu, Dec 18, 2003, Philip L Smith wrote: > Hi Lutz > > Have run with ssldump, there doesn't seem to be any session_id being > sent from the client. > > I presume it would show up something like session_id[32]=... under the > C>S Handshake section. > > What else might I be doing wrong, or

SSL_R_DIGEST_CHECK_FAILED

We have a 0.9.6-based client talking to a 0.9.7a-based mod_ssl server. The error the client is receiving is a handshake error 40 (0x28). The error description generated in the Apache error log is: Library Error: 336117909 error:1408C095:lib(20):func(140):reason(149) lib 20: SSL Library func 140: E

Re: Session not re-used when exported then re-imported.

This may not be the problem but that PEM stuff looks decidedly dodgy. Just do: s = PEM_read_SSL_SESSION(filePtr, NULL, NULL, NULL); Hi Steve This was it ! Not sure where I got it from anyway. All is now running fine with the client sending the session_id in the resume string.

valgrind reports failures on examples

I was getting a _lot_ of valgrind failures on my code using OpenSSL. I tried to simplify things by just running the examples included in the distribution. valgrind is still reporting a lot of bugs on all the examples. (428489 errors from 1928 contexts on ssl_test.) Most of the errors seem to be

Re: valgrind reports failures on examples

Scott Lamb wrote: Has anyone run these examples through valgrind before? Have you found similar problems? Yes, I've had similar problems with openSSL 0.9.6. I was getting this kind of error messages when runing both my appllication and openssl s_client under valgrind. So far I was unable to fi

Re: valgrind reports failures on examples

Michal Dobaczewski wrote: Scott Lamb wrote: Has anyone run these examples through valgrind before? Have you found similar problems? Yes, I've had similar problems with openSSL 0.9.6. I was getting this kind of error messages when runing both my appllication and openssl s_client under valgrind

NEWBIE: The man pages in a PDF file

Title: NEWBIE: The man pages in a PDF file Sorry, this is a really naïve question.  I'm really getting a lot out of the man pages once I figured out how to dig through it.  But it's time-consuming to pick and choose the sections to print.  Does anyone know whether there a PDF version of the

Re: valgrind reports failures on examples

Scott Lamb wrote: Maybe I should also mention that my library and unit tests are multi-threaded. (I have defined the appropriate locking callbacks.) I could easily see how that'd aggravate any problems. I forgot to mention: I'm also using a debug malloc library (). So wh

RE: valgrind reports failures on examples

> Most of the errors seem to be in one of these classes: > - Conditional jump or move depends on uninitialised value(s) > - Use of uninitialized value > > When I run it in my own code (which seems correct to me), I > see this also: > - Syscall param write(buf) contains uninitialised or > unaddressa

Re: valgrind reports failures on examples

Syscall write(buf) contains uninitialized or unaddressable bytes doesn't mean that it's sending uninitialized memory. I've run across this one a number of times when dealing with socket code. If you allocate say a 64k buffer (~ max datagram size) and then call send() with a length of 100 byt

Re: NEWBIE: The man pages in a PDF file

On Thu, Dec 18, 2003 at 01:03:55PM -0500, mclellan, dave wrote: > Does anyone know whether there a PDF version of the man pages somewhere in > the world? Individual sections? pod2pdf may help: http://search.cpan.org/~ajfry/Pod-Pdf-1.2/scripts/pod2pdf I'm sure POD indexers exist, so with some

Windows version?

I'm sure this has to be a common question. Where can I find a Windows command line version of OpenSSL? (Or, how do you make one?) Thanks. Christian Malone __ OpenSSL Project http://www.openssl.org

Re: Windows version?

At 06:44 PM 12/18/2003 -0800, Christian Malone writeth: >I'm sure this has to be a common question. >Where can I find a Windows command line version of OpenSSL? >(Or, how do you make one?) http://www.shininglightpro.com/search.php?searchname=Win32+OpenSSL Hope this helps! Thomas J. Hr

RE: Libssl chooses wrong cipher suite during TLS authentication

On Wed, Dec 17, 2003, Dr. Stephen Henson wrote: > IIRC the client hello reports the supported ciphersuites in order of preference and > the OpenSSL server code will > normally use the first one from that list that it supports. The actual ciphersuites > supported by the server may be > less than

Re: Libssl chooses wrong cipher suite during TLS authentication

On Thu, Dec 18, 2003 at 08:02:46AM +0100, Obermeier Markus ICM MP PD TS wrote: > On Wed, Dec 17, 2003, Dr. Stephen Henson wrote: > > > IIRC the client hello reports the supported ciphersuites in order of preference > > and the OpenSSL server code will > > normally use the first one from that list

Re: unresolved symbol error on HP

In message <[EMAIL PROTECTED]> on Wed, 17 Dec 2003 17:14:46 -0700, [EMAIL PROTECTED] said: abalan> I used a preexisting build of openssl 0.9.7b, which was built on HP-UX abalan> 11.00. abalan> abalan> the command I used to link the program together is; abalan> abalan> ld -a default -b -o libte

Re: Session not re-used when exported then re-imported.

On Wed, Dec 17, 2003 at 03:37:19PM +, Philip L Smith wrote: > I connect fine from one process, display it's details using a version of > SSL_SESSION_print(out,x) > (taken from sess_id.c), then save the session in use to a file ... > This is the output from the session that works > > Protocol

Re: Session not re-used when exported then re-imported.

Lutz Jaenicke wrote: On Wed, Dec 17, 2003 at 03:37:19PM +, Philip L Smith wrote: I connect fine from one process, display it's details using a version of SSL_SESSION_print(out,x) (taken from sess_id.c), then save the session in use to a file ... This is the output from the sessi

Re: Session not re-used when exported then re-imported.

On Thu, Dec 18, 2003 at 10:13:27AM +, Philip L Smith wrote: > >Changes between 0.9.6g and 0.9.6h [5 Dec 2002] > >... > > *) Bugfix: client side session caching did not work with external caching, > >because the session->cipher setting was not restored when reloading > >from the externa