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
I'm going to go ahead and say that GPU drivers will never get this right. Those things are such massive hairballs that if you enable eGPU support over an external interface, you have to assume you're immediately pwnable.
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.
So Thunderbolt device authorization will prevent this attack?
Not using Thunderbolt will prevent this attack, because I doubt there is a single Thunderbolt device driver that is secure.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
