News for hackers. Stuff that matters.
Re:PoisonTap (2016) by stedaniels on Friday September 27, 2019 @02:33AM (#21089055)
Re:PoisonTap (2016) by mirimir on Friday September 27, 2019 @02:55AM (#21089183)
Huh.

Maybe I'm naive, but wouldn't iptables block it?

Default rules on the host box that this VM runs on include:

    -A OUTPUT -o eth0 -d 192.168.1.0/24 -j ACCEPT
    -A OUTPUT -o eth0 -d 1.2.3.4/32 -j ACCEPT
    -A OUTPUT -o tun0 -j ACCEPT
    -A OUTPUT -j DROP
With 1.2.3.4 being the VPN server that I'm using. And VirtualBox doesn't have USB enabled.

And if I weren't using a VPN, it'd be:

    -A OUTPUT -o eth0 -j ACCEPT
    -A OUTPUT -j DROP
So nothing would use a new interface, no matter what routing it promised. And even in Windows, decent VPN client apps use rules that are basically analogous to those.
Re:PoisonTap (2016) by regecks on Friday September 27, 2019 @02:46AM (#21089126)
usgbuard is another countermeasure if you have a Linux workstation.
Re:PoisonTap (2016) by xnzakg on Friday September 27, 2019 @02:59AM (#21089202)
Wouldn't simply disabling automatic connection to wired networks work against this? Weird not to see that mentioned in the potential countermeasures.
Re:PoisonTap (2016) by emmelaich on Friday September 27, 2019 @01:53AM (#21088854)
[2016]

Still cool though!

Re:PoisonTap (2016) by dang on Friday September 27, 2019 @02:49AM (#21089151)
Added. Thanks!