Because NaCl code isn't arbitrary, it has to follow certain rules so that it can be validated. If an errata requires a specific code sequence, and that code sequence is impossible to validate, then please explain how it's relevant.
-
-
Are you saying that, NaCl validated code cannot hit CPU data corruption bugs? Or that NaCl is robust against arbitrary data corruption including corruption of IP?
1 reply 0 retweets 1 like -
You read the previous tweet, and concluded I must be saying that NaCl cannot hit any future undiscovered CPU data corruption? I cannot help thinking that is a bad faith interpretation Dan.
2 replies 0 retweets 0 likes -
It is literally my point that Intel and AMD make chips that are much more complex than the vendors you ban and therefore have a lot more data corruption bugs. You're saying that point is an inherently bad faith argument?
1 reply 0 retweets 2 likes -
Yes. NaCl requires a few obscure areas to work under adversarial conditions in a very predictable way that we can test, how is it relevant that other areas can fail?
1 reply 0 retweets 1 like -
You specifically said you were concerned about executing the wrong code and I linked to one such bug and noted that Intel has more of these kinds of bugs than other vendors. Are you now saying that was a red herring and you're not concerned about that kind of bug?
1 reply 0 retweets 1 like -
Holy moly. NaCl works by validating code conforms to certain requirements, and that requires being able to accurately predict control flow. However, NaCl is not arbitrary, it's a small whitelist of instructions sandboxed with segmentation.
1 reply 0 retweets 1 like -
I need to get dinner. I don't think Twitter is a great venue for this discussion. If you'd like to talk about why I don't think whitelisting instructions can address the kinds of bugs I've mentioned, I'd be happy to hop on a call to discuss.
1 reply 0 retweets 0 likes -
I have to say, I can't say I'm particularly interested in your opinion of a paper you haven't read. I don't think you understand the security model, which perhaps you should have made an effort to do before criticizing.
1 reply 0 retweets 0 likes -
What is this paper? Where could I read it? I find these sort of HW/Sw codesign challenges very interesting!
1 reply 0 retweets 0 likes
This is it, it's a software fault isolation system for x86. It's no longer used, but was widely deployed for a while. https://research.google.com/pubs/archive/34913.pdf …
-
-
Replying to @taviso @TheKanter and
I think this discussion perfectly illustrates why it’s great that NaCl died. Thankfully we have WASM which more than fills the vacuum.
1 reply 0 retweets 0 likes -
Replying to @iamtommythorn @TheKanter and
I guess I don't follow? I think NaCl had a number of problems, none of them were mentioned in this thread though. Not really sure what my opinion of WASM is, but I like it a lot better than asm.js.
1 reply 0 retweets 0 likes - 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.