Fix glitch with HelloVerifyRequest

With the close-rebind strategy, sometimes the second ClientHello was lost (if
received before close), and since our client doesn't resend yet, the tests
would fail (no problem with other client that resend). Anyway, it's not really
clean to lose messages.
This commit is contained in:
Manuel Pégourié-Gonnard 2014-08-07 17:21:47 +02:00 committed by Paul Bakker
parent 562eb787ec
commit 4ba6ab6d0d

View File

@ -1522,22 +1522,26 @@ reset:
if( client_fd != -1 )
{
net_close( client_fd );
/*
* With UDP, client_fd == bind_fd, so we just closed bind_fd. Bind it
* again. (We really want to close it, to empty the message queue.)
*/
#if defined(POLARSSL_SSL_PROTO_DTLS)
if( opt.transport == SSL_TRANSPORT_DATAGRAM )
{
/* Keep the connection open if waiting for client to continue */
if( ret != POLARSSL_ERR_SSL_HELLO_VERIFY_REQUIRED )
{
net_close( client_fd );
/*
* With UDP, client_fd == bind_fd, so we just closed bind_fd.
* Bind it again. (We really want to close it, to empty the
* message queue.)
*/
printf( " . Bind on udp://%s:%-4d/ ...",
opt.server_addr ? opt.server_addr : "*",
opt.server_port );
fflush( stdout );
if( ( ret = net_bind( &listen_fd, opt.server_addr, opt.server_port,
NET_PROTO_UDP ) ) != 0 )
if( ( ret = net_bind( &listen_fd, opt.server_addr,
opt.server_port, NET_PROTO_UDP ) ) != 0 )
{
printf( " failed\n ! net_bind returned -0x%x\n\n", -ret );
goto exit;
@ -1545,7 +1549,10 @@ reset:
printf( " ok\n" );
}
}
else
#endif /* POLARSSL_SSL_PROTO_DTLS */
net_close( client_fd );
}
ssl_session_reset( &ssl );