On Tue, 16 Feb 1999, White Cap wrote:
>
> On Tue, 16 Feb 1999, Fyodor wrote:
>
> > This is not actually my reason for disapproval. The reason I don't plan
> > on adding this it is that it only works in the very specific case
> > where:
> >
> > 1) You are using ethernet
> > 2) Your target is using ethernet
> > 3) You are on the *same* ethernet segment
> >
> > I don't think it is worth the code bloat or confusion to add such a
> > special-case feature. Plus you should generally be able to do an
> > 'arp -a' after the scan and see what hardware address the target
> > (or several targets) are using.
>
> A compile time option maybe? maybe force the user to define
> WANT_ARP_CHECK?
>
> And maybe another one for WANT_PROMISC_MODE_DETECTION?
>
>
> whitecap
>
if this kind of thing is to be implemented at all, i dont think it should
be a precompiler defintion. i think it should be a command line option,
and the option,if specified, should only take effect if scanning a
local segment and if the process has root priv (duh).
i think making that into a #define is just getting way out of scope
my two cents
ajax_at_mobis.com | The skill of accurate perception
Unix Network Admin | is called cynicism by those who
Mobile Internet Services, Inc. | don't possess it.
Received on Feb 16 1999
Intro
