Original message
>Date: Sat, 12 Jan 2008 03:42:36 -0800
>From: "Ted Mittelstaedt" <[EMAIL PROTECTED]>
> The easiest way is to have the user install a random
> device. There's ones out there
> for Solaris all the way back to version 2.5.1
>
> However, keep in mind that al
>Hello,
>> We have a web server running on Apache/Tomcat platform (Sun Solaris 10)
>> with a VeriSign certificate. I'm trying to use the same certificate with
>> openssl 0.9.8f for my stand-alone web services application (listening on
>> separate ports, of course). So I followed the procedure a
>> Storing some fingerprint of a certificate or public key locally
>> in some trusted place (such as a local file system) seems to be
>> quite secure (should be the same level as having a CAs root
>> certificate in a file), however, I'm not sure if this works with
>> OpenSSL which seems to expect t
Original message
>Date: Fri, 30 Mar 2007 12:01:54 -0700
>From: "David Schwartz" <[EMAIL PROTECTED]>
>Subject: RE: SSL_connect and SSL_accept
>To:
>
>
>> So what you are saying is the scenario we have been discussing so far is
>> possible ONLY in case of memory allocation issues NOT O
>> Since he's talking about a process that forks, there
>> shouldn't be a problem.
>> He just needs to create a shared mapping in the parent. After
>> the 'fork', the address will still be the same.
>
>However if the program forks and calls exec* then this issue could
>arise. The title of the th
Original message
>Date: Tue, 29 Aug 2006 19:02:32 +0200
>From: Marek Marcola <[EMAIL PROTECTED]>
>Subject: Re: Build problem on HP Itanium 64 bit machine
>To: openssl-users@openssl.org
>
>Hello,
>>
>> I am having problem building openssl on HP Itanium 64 bit box.
>> Attached are th
Original message
>Date: Tue, 29 Aug 2006 20:05:51 +0200
>From: Leif Thuresson <[EMAIL PROTECTED]>
>Subject: Re: Build problem on HP Itanium 64 bit machine
>To: openssl-users@openssl.org
>
>Hi,
>I have also had problems building shared version of
openssl-0.9.8b
> on hpux-11.00 parisc
Original message
>Date: Tue, 22 Aug 2006 12:22:37 -0700
>From: "David Schwartz" <[EMAIL PROTECTED]>
>Subject: RE: Wrapping SSL_read/SSL_write so they behave like
read/write.]
>To:
> You should 'select' for writability if and only if you get a
WANT_WRITE
>indication, whether
Original message
>Date: Tue, 22 Aug 2006 15:00:46 +0200
>From: Marek Marcola <[EMAIL PROTECTED]>
>Subject: Re: Wrapping SSL_read/SSL_write so they behave like
read/write.]
>To: openssl-users@openssl.org
>You may use select() but with some care.
>Simplest way is to:
> 1) wait on sele
Hi,
Thanks for the explanation of the data exchanged between the
client and server.
>In response to client_hello we received ALERT protocol
message
>(record header 15 03 00 00 02 means:
> 15 - alert protocol
> 0300 - SSL3 alert protocol
> 0002 - length of data (should be 2 - an
10 matches
Mail list logo