Re: nmap does not list ciphers consistently

Anil,

Are you using the same version of Nmap on both Mac and Windows? The current
version of the script uses Nmap's discovered timeout value (about .2
seconds in your case) plus 5 seconds. This ought to be very generous for
the initial TCP connection, and we thought it was sufficient for the
subsequent TLS handshake. Nmap 6.47 and earlier used a static 5-second
timeout, which is close enough to be the same in your case.

Dan

On Thu, Feb 8, 2018 at 8:05 PM, <[email protected]> wrote:

> Hi Daniel, It seems nmap behavior is different on Mac OS vs Windows OS. As
> per a test done on a Windows following nmap command with "min/max rtt
> timeout value of 10sec" does consistency list the Ciphers.
>
> What would be the logic behind it why RTT of 10 sec on direct attach would
> make any difference. Is is any delayed response from the target IP which
> was causing possible failure ? Why is this so sensitive in Windows?
>
> nmap.exe *--max-rtt-timeout 10000ms --min-rtt-timeout 10000ms *--script
> ssl-enum-ciphers <ClusterIP-Address> -p 443
>
> Regards
> Anil.
>

_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/