If you have a #Thunderbolt capable computer, read this:
Despite the fancy name, plugging in unknown devices is probably always going to be a huge risk & I honestly can't think of a scenario where you'd be plugging in something you found on the parking lot if you at all care about security.
Now there are of course risks such as having your charger secretly exchanged for a malicious one, but if the attacker is this determined, you probably need a whole new strategy.
Seeing the massive performance degradation that #Spectre & #Meltdown fixes could cause, (up to 30% in some workloads), am not even sure their current approach is wrong in the general case. It seems to be a case of performance vs maximum security, pick one.
So it may end up being the case that we'll need to think about security a lot more explicitly/manually ourselves when performing certain actions, rather than simply relying on the OS to somehow shield us. It seems logical to me that no matter how hard we try, once an attacker has physical access, there's little one can do to stop them.
@TheCzar Agreed. I think part of the reason why HW security lags is also because unlike software, where developers can live off one SW for years, so it's worth paying some attention to security bugs etc. whereas with hardware, it's usually 'done' once on the market and the OEM is already working on the next one, no time to fundamentally redesign anything.
Of course the barriers to hardware verification and security testing are also much higher, as you say, so it doesn't get much attention.
Hi there! I am a free software developer. I enjoy working on useful software, as well as advocating for software freedom and the use of open standards, promoting data ownership, decentralization and privacy. If this is important to you, I may be worth following. If you like Go, Rust, or Swift, it may be worth following me as well. Besides computing, I enjoy metal, a good read and occasionally some gaming, (not much time for that these days).