NSOCK INFO [6.9340s] handle_connect_result(): EID 9 reconnecting with SSL_OP_NO_SSLv2
NSOCK INFO [6.9760s] nsock_readbytes(): Read request for 5 bytes from IOD #104 [192.34.1.207:3389] EID 2482
NSOCK INFO [6.9760s] handle_connect_result(): EID 9 reconnecting with SSL_OP_NO_SSLv2
NSOCK INFO [6.9760s] nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 2482 [192.34.1.207:3389] (855 bytes)
NSOCK INFO [7.0170s] handle_connect_result(): EID 9 reconnecting with SSL_OP_NO_SSLv2
NSOCK INFO [7.0240s] nsock_iod_delete(): nsock_iod_delete (IOD #104)
NSOCK INFO [7.0670s] handle_connect_result(): EID 9 reconnecting with SSL_OP_NO_SSLv2
NSOCK INFO [7.1100s] handle_connect_result(): EID 9 reconnecting with SSL_OP_NO_SSLv2
NSOCK INFO [7.1530s] handle_connect_result(): EID 9 reconnecting with SSL_OP_NO_SSLv2
NSOCK INFO [7.1960s] handle_connect_result(): EID 9 reconnecting with SSL_OP_NO_SSLv2
NSOCK INFO [7.2430s] handle_connect_result(): EID 9 reconnecting with SSL_OP_NO_SSLv2
NSOCK INFO [7.2940s] handle_connect_result(): EID 9 reconnecting with SSL_OP_NO_SSLv2
NSOCK INFO [7.3370s] handle_connect_result(): EID 9 reconnecting with SSL_OP_NO_SSLv2
NSOCK INFO [7.3890s] handle_connect_result(): EID 9 reconnecting with SSL_OP_NO_SSLv2
NSOCK INFO [7.4310s] handle_connect_result(): EID 9 reconnecting with SSL_OP_NO_SSLv2
...
...
NSOCK INFO [30.0460s] handle_connect_result(): EID 9 reconnecting with SSL_OP_NO_SSLv2
NSOCK INFO [30.4530s] nsock_trace_handler_callback(): Callback: SSL-CONNECT TIMEOUT for EID 9 [192.34.1.207:3389]
NSOCK INFO [30.4530s] nsock_iod_delete(): nsock_iod_delete (IOD #1)
NSOCK INFO [30.4530s] nsock_iod_delete(): nsock_iod_delete: SSL shutdown failed ((null)) on NSI 1
Describe the bug
We observed the Nmap
ssl-cert
used by the TCP-probe to get stuck in a loop and thus timeout.To Reproduce
The following Nmap command can be used to reproduce the issue:
In this case the host
192.34.1.207
runs Microsoft Windows Server 2008 R2 Standard The only port open and thus checked is3389
.Next, we ran the
nmap
command with the debug option:-d --packet-trace
:This produced the following output:
After 30 seconds, the loop is aborted.