Responder

These tool installs are based on the existence of virtualenv.

apt update
apt install python3-virtualenv

Note on virtualenv usage:

• these containers are used to allow conflicting dependency installs to live side by side harmoniously
• activate / deactivate dependency containers for proper usage
  • prompt# source demo-env/bin/activate
  • prompt(demo-env)# deactivate
• with screen/tmux, multiple dependency containers can be activated at the same time

Responder

Overview: Swiss Army network poisoner. DHCP, mDNS, NBNS, LLMNR, and more.

Tool available here

Possible Blurb: BHIS used the Responder toolkit to both review the layer two protocols in transit on the >IP RANGE< network and poison various protocol requests as appropriate to demonstrate impact. Some of the protocols the testers were investigating included LLMNR, NBNS, and mDNS. These protocols generate specific traffic that can be poisoned or abused for exploitation.

Installation

cd /opt/
git clone https://github.com/lgandx/Responder.git
cd Responder
virtualenv -p python3 resp-env
source resp-env/bin/activate
python3 -m pip install wheel
python3 -m pip install -r requirements.txt
deactivate
cd /opt/

Help

python3 Responder.py -h

Basic Usage

These are not your only options. Be careful with the -d flag, it can cause network disruptions as your implant becomes a DHCP server on the local network/broadcast domain.

python3 Responder.py -i eth0 -wvF
#### description of usage below (do not paste)
-w: wpad
-v: verbose
-F: force wpad auth #we want http auth for relay