3 ms·
I mean, just look at the commits with "fix" in the specs folder: https://github.com/seL4/l4v/commits/master?after=4f0bbd4fcbc850ee00e2b111e861bdb79172c341+244&b
by jcelerier 4y ago
I mean, just look at the commits with "fix" in the specs folder: https://github.com/seL4/l4v/commits/master?after=4f0bbd4fcbc850ee00e2b111e861bdb79172c341+244&branch=master&path%5B%5D=spec&qualified_name=refs%2Fheads%2Fmaster https://github.com/seL4/l4v/commits/master?after=4f0bbd4fcbc...
- Jweb_Guru 4y agoNone of the "issues" in the first few pages look serious (most of them seem to be about portability to new architectures), so why don't we save some time and have you link to the specification bug you believe undermined the security guarantees of the system? So far you have only asserted such a bug exists.
- jcelerier 4y agoWhy are you talking about security guarantees? A bug is a bug, the point is to show that formal specifications don't prevent bugs. In some cases a warning text not showing up due to a bug or the wrong byte being sent to the serial port can have more severe consequences that any CVE-assignable issue.