To: [EMAIL PROTECTED]
Subject: Re: renegotiation in 0.9.7
On Mon, Jan 27, 2003 at 03:21:45PM -, Nigel Spowage wrote:
okay, so the proper way to renegotiate a connection is :
1 - call SSL_renegotiate()
2 - call SSL_do_handshake()
3 - wait for either
3a
On Thu, Jan 30, 2003 at 10:41:08AM -, Nigel Spowage wrote:
my client app calls SSL_renegotiate() and gets a return value of 1
(success i presume, as i cann't find a man page for this
function). this sets up internal flags in ssl ready to negotiate the
connection.
i call
To guess what is going on, I'd have to know
- whether your application is operating as a client or a server
(an SSL/TLS client apparently) and
yep, it's a client. is the renegotiation code different for a client than for a server
?
- what protocol version is used.
SSL 2.0 does not
On Mon, Jan 27, 2003 at 03:21:45PM -, Nigel Spowage wrote:
okay, so the proper way to renegotiate a connection is :
1 - call SSL_renegotiate()
2 - call SSL_do_handshake()
3 - wait for either
3a- SSL_renegotiate_pending() to return 0, or
3b- an acceptable amount of time (which means
On Mon, Jan 27, 2003 at 10:33:44AM -, Nigel Spowage wrote:
i'm currently trying to implement ssl renegotiation for an
application which uses openssl in a non-blocking mode.
SSL_renegotiate(ssl);
result = SSL_do_handshake(ssl);
/* result is okay at this point */
/* my app waits for a
am i missing something ? is there something extra i need to do ?
Yes, call SSL_renegotiate() to initiate a second handshake once the
first one has finished. Otherwise SSL_do_handshake() does not think
that there is something to do for it.
okay, so the proper way to renegotiate a
