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
It's the easiest way to fix these flaws: have a fundamentally separate SoC with a small attack surface in a purely management role, which is responsible for confirming main CPU's behavior is in line with expectations. Like ME, but external and auditable.
How would this work? If it has to monitor everything the main CPU does, it has to be as powerful as the main CPU. If it doesn't, then you could make the main CPU do evil things that it wouldn't catch.
It wouldn’t be to different from monitoring software currently used. The goal is detection of malicious activity, so if you can do classification and identification fast enough you don’t need to replicate the CPU.
I mean, we all know antivirus doesn't work. Reactive technologies are great and all, but how would you fundamentally distinguish malicious behavior from normal operation besides known signatures?
I'm not thinking of a full monitoring role, was juggling a million notifications when I saw this. My main motivation for this is the thought of ME/other management coprocessors which are unaudited attack surfaces.
I guess my main thought is that a separate, replacable, open source, simple processor for handling trusted execution tasks adds a level of security and peace of mind. It doesn't fix side-channels, but it does allow for verification of no sidechannels in trusted environments
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
