And USB at the heart of it. My old friend, USB.
Why am I not surprised?
11–20 of 57 posts
And USB at the heart of it. My old friend, USB.
Why am I not surprised?
"PoisonTap, a $5 tool that invades password-protected computers"
[1] https://en.wikipedia.org/wiki/Samy_Kamkar [2] https://hn.algolia.com/?query=tptacek%20"physical%20access"&...
It's long past time that USB security is taken seriously. By default anything stuck into a USB port should be sandboxed and various integrity checks need to be performed before access is allowed.
Yes, suppose you have a mac mini and you plug in USB keyboard, oops it's sandboxed and does not work.
It seems like another mitigation missing from their list is "modify your DHCP client to reject over-broad subnet masks" where the cutoff is probably something like /20. Additionally you could reject any DHCP lease for a subnet that purports to overlap with the address range of any other directly connected network.
It seems like another mitigation missing from their list is "modify your DHCP client to reject over-broad subnet masks" where the cutoff is probably something like /20. Additionally you could reject any DHCP lease for a subnet that purports to overlap with the address range of any other directly connected network.
It seems like another mitigation missing from their list is "modify your DHCP client to reject over-broad subnet masks" where the cutoff is probably something like /20. Additionally you could reject any DHCP lease for a subnet that purports to overlap with the address range of any other directly connected network.
Couldn't the USB device identify itself as multiple devices over the same port? Similar to a hub. It could then give a /20 to each device.
If so -- assuming the user is logged in to {1Password|LastPass} -- just plug this in to their PC after they walked away from their desk and wait for all of their saved credentials to be stolen!
It was a decent (but not very popular) defense against rootkits and attackers being able to dynamically load kernel modules and would also prevent something like this (unless you had the necessary drivers compiled in).