Minimize the attack footprint

[disconsis]

Basically, make the attack as sneaky as possible.
It probably won't fool an IDS anytime soon (it is just an ARP spoof ffs), but I'd like to not make the attack completely obvious to anyone who happens to have Wireshark open at the time.
That said, this is more of a stretch goal than anything else, and this issue will be around for quite some time.

• For starters, I'd like to not send ARP replies to everyone on the subnet when there's only a few targets. So no broadcast ARP replies.
• Find hosts that might be monitoring the attack and "deal" with them (Find hosts potentially monitoring the attack #4)
• Add options to change delays between steps.

More tasks will be added here as I learn about other methods of ARP spoofing detection.

[disconsis]

• Change source address of ARP requests. Preferably to that of a live host, if checking this doesn't increase the attack fingerprint by itself.

Also, if potential monitor hosts are found (as in #4), their addresses shouldn't be set as the source address.

We can still read the replies on promiscuous mode.

We would have a problem if the subnet was fragmented (since then we'd never receive those requests) but since we're spoofing the gateway, that use case is murky at best. I'll have to resolve this though.