News for hackers. Stuff that matters.
Re:The reckless, infinite scope of web browsers by hajile on Wednesday March 18, 2020 @11:24AM (#22617632)
The difference is that Java bytecode is fundamentally insecure. Wasm seems to take inspiration from the research that went into NaCl/pNaCl.
Re:The reckless, infinite scope of web browsers by cesarb on Wednesday March 18, 2020 @01:11PM (#22618881)
The worst problem with the Java sandbox was not the bytecode (though it did have its share of bytecode validation bugs). The worst problem was the vast API surface with its "blacklist" security model: all methods which should not be called from the sandbox have to explicitly call a AccessController.checkPermission() or similar. Miss one, and you have a hole in the sandbox. WASM instead follows a "whitelist" approach, which is much more robust.
Re:The reckless, infinite scope of web browsers by Pyxl101 on Wednesday March 18, 2020 @07:42PM (#22622705)
How is Java bytecode fundamentally insecure? (Example?)