You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
So whitelist Thunderbolt devices to... well, zero devices, to start with. Then start auditing and rewriting drivers and *only* whitelist for TB access those where all of the aforementioned concerns have been considered, possibly in a complete rewrite. It won't be easy.
You'll still have bugs, but, like, the current state of things is that nobody has even *considered* any of this. Right now it's not bugs, evil-device security is literally outside the scope of basically every PCIe driver right now.
I am a believer in coarse grained security. There are indefensible boundaries. Imagine if JavaScript on web pages tried to be more granular than same origin.
Anything remotely plug and play should be moderately safe to do so by design.
What about evil displays, (e)SATA, SIM etc ? *NOT* thinking about evil onboard or RAM chips ... Any idea how to not get paranoid ?
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
