On Tue, Jun 20, 2006 at 07:03:49PM +0200, Kurt Roeckx wrote:
>> Applications are also expected to provide a thread ID callback by
>> calling CRYPTO_set_id_callback(), although the failure to do so should
>> not be a problem on Linux where different threads run with different
>> PIDs, since OpenSSL
On Fri, Jun 23, 2006 at 05:21:37PM +0200, Bodo Moeller wrote:
> OpenSSL CVS Repository
> http://cvs.openssl.org/
>
>
> Server: cvs.openssl.org Name: Bodo Moeller
> Root: /v/openssl/cvs
Hello Matt,
I am interested in your issue with:
SSL_shutdown(ssl);
SSL_free(ssl);
causing disruption of other SSL connections open within the same
application.
There should be nothing wrong not checking the return values of
SSL_shutdown() is your application does not need a guaranteed end o
On Fri, Jun 23, 2006 at 04:36:07PM +0100, Joe Orton wrote:
> >
> > Log:
> > New functions CRYPTO_set_idptr_callback(),
> > CRYPTO_get_idptr_callback(), CRYPTO_thread_idptr() for a 'void *' type
> > thread ID, since the 'unsigned long' type of the existing thread ID
> > does not a
Hi Darryl,
As you suspect we don't really need guaranteed secure stream
termination, so really all I was interested in was closing the socket
cleanly.
I also suspected an application programming error on my part, but I
really couldn't track it down, and as I say using the same method that
Stunne
On Fri, Jun 23, 2006 at 06:42:10PM +0200, Kurt Roeckx wrote:
> On Fri, Jun 23, 2006 at 04:36:07PM +0100, Joe Orton wrote:
>>> Log:
>>> New functions CRYPTO_set_idptr_callback(),
>>> CRYPTO_get_idptr_callback(), CRYPTO_thread_idptr() for a 'void *' type
>>> thread ID, since the 'unsig
Is this RFC supported in current version of openssl?http://www.ietf.org/rfc/rfc3546.txtthanks,Weidong
This message should have gone to the openssl-users list.
To answer your question, it depends on what you mean by "supports".
There is currently no means in place to define your own extension ID
numbers and write handlers for them, to possibly modify the SSL_CTX or
SSL structure that is associate
