Re: [NSE] ntp-monlist

[Richard Miles <richard.k.miles () googlemail com>]

Thanks, it really answered my question. It's nice to know that we can
use NTP to discover internal IP address of a network, I was not aware
of it. It's a flaw on the implementation? Bad configuration? Or a bad
design of the protocol?

thanks

On Sun, May 30, 2010 at 5:09 PM, jah <jah () zadkiel plus com> wrote:
> On 30/05/2010 16:33, Richard Miles wrote:
> > What mean public clients and private clients?
> Hello Richard,
>
> The script categorises the hosts in the monitor list into:
>
> Servers - The target is configured to obtain time from these hosts in
> client/server mode. For example, an NTP daemon on the target has an
> /etc/ntp.conf entry such as "server <IP_Address>".
> Peers - The target is configured to obtain time from these hosts in
> Symmetric Active mode. For example, an NTP daemon on the target has an
> /etc/ntp.conf entry such as "peer <IP_Address>". Additionally, these
> hosts may be NTP daemons which are configured with the target as a peer.
> Clients - simply those hosts who contact the target to obtain time,
> either in symmetric active mode or client/server mode.
> Others - hosts who have sent NTP Control Mode or Private Mode
> requests/commands to the target.
>
> Private servers, peers and clients are hosts with private or special use
> IP addresses e.g. from 192.168.0.0/16 etc.  If you're scanning a target
> across the internet then any Private addresses will be of interest to
> you since they may help to understand the topology of the remote private
> network.
> Public servers, peers and clients are hosts without private or special
> use IP addresses.
> Specifically, ipOps.isPrivate() is used to determine whether or not an
> IP address is private or not.
>
> Does that answer your question?
>
> jah
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/