4 ms·
I mean, this class of attack is defeated as a matter of course in high reliability applications like aerospace. You just check the compiler output precisely cor
by Veserv 3y ago
I mean, this class of attack is defeated as a matter of course in high reliability applications like aerospace. You just check the compiler output precisely corresponds to the compiler input. You need to do that anyways to prevent miscompilation errors in general (this class of attack is just intentional miscompilation), so it hardly counts as a nightmarish problem, just a annoying one.
- azornathogron 3y agoHow is this normally done? Manual review of machine code?
- Veserv 3y agoI do not work on verification directly, so I do not know the details. I believe at a high level you generally have a automated first pass which generates a source<->machine trace. You then have multiple independent reviews validating the correctness and exhaustiveness of the trace. Generally in these environments you build with optimizations off unless needed to ease this validation process as, obviously, you must validate the released/deployed version.
- kwhitefoot 3y ago> You just check the compiler output precisely corresponds to the compiler input. just is doing a lot of work there.
- Veserv 3y agoWhat do you want me to say? That is the work that you must do and that is routinely done. It is annoying, but it is not hard or special. Hardly a nightmarish problem if it gets solved routinely at scale across a entire industry.