Anyone want to place bets on whether the first actual fix for Spectre will be via reverse engineered and patched microcode?https://twitter.com/thorstenholz/status/1031839729145311232 …
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
Consider an emulator written in whatever language with fancy array bounds you like, emulating a machine running untrusted code in multiple privilege domains. Data is all just one big array, bounds do nothing.
I like the idea of a randomised ISA so that payloads need to first crack a high entropy dynamically randomised ISA. Google “crypto binary translation”
This has no relevance to the topic at hand because the attack code doesn't have any relation to the host ISA and no need to know anything about the host running the emulator.
We can also solve L1TF with shadow paging. This was the original rationale for the work on the rv8 JIT engine. Use RISC-V as the IR for dynamic runtime translation/obfuscation with multiple entropy vectors. RISC via CISC to a microop backend. It is however a bit of a pipe dream.
Do you mean Foreshadow? AIUI it's solvable just by not putting data in the unused private bits of not-present PTEs.
But given how awful Intel's been I'd be tempted just to not use PTEs at all, TLBs only, faulting on every miss.
Bounds are valuable. Have you read the Cambridge CHERI papers? Checked C on CHERI would probably have enough metadata to speculate safely.
No, because it's not relevant - the classification as "safe" is mistaken. If it's possible for an attacker to time reading a2[a1[i]] where all the indices are valid but where the correctly-taken branches preclude the access with this value of i, you have a Spectre v1 vuln.
But transactional caches that avoid evocation side channels can fix it in future processors. CPUs have 3-5 year maximum life anyhow. Ya just get a server with Coldfire M68K chips. None of the sploit payloads will work.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.