Nmap Development mailing list archives
Re: [NSE] ntp-info probing logic?
From: nnposter () users sourceforge net
Date: Thu, 7 Aug 2014 23:12:25 +0000
Back in March I have proposed a change in how ntp-info behaves to improve its compatibility. http://seclists.org/nmap-dev/2014/q1/341 nnposter wrote:
The current version of ntp-info.nse has the following flow: 1. Send NTPv4 request for date/time 2. Exit if it failed 3. Save results 4. Send NTPv2 request for readlist 5. Save results (if any) 6. Return all saved results I am wondering if anybody has any insight into the reason behind the early bailout in step 2. I am seeing systems where the first probe in step 1 fails but the second probe in step 4 does not. In case there is no good reason to keep the current logic then I am proposing the patch below, effectively removing step 2/3.
The proposal has not received any feedback so I would like to ask for a reconsideration or some explanation why it would be a bad idea. Cheers, nnposter _______________________________________________ Sent through the dev mailing list http://nmap.org/mailman/listinfo/dev Archived at http://seclists.org/nmap-dev/
Current thread:
- Re: [NSE] ntp-info probing logic? nnposter (Aug 07)
- Re: [NSE] ntp-info probing logic? Daniel Miller (Aug 20)
- Re: [NSE] ntp-info probing logic? nnposter (Aug 22)
- Re: [NSE] ntp-info probing logic? Daniel Miller (Aug 23)
- Re: [NSE] ntp-info probing logic? nnposter (Aug 26)
- Re: [NSE] ntp-info probing logic? nnposter (Aug 22)
- Re: [NSE] ntp-info probing logic? Daniel Miller (Aug 20)
