4 ms·
sounds like java's SecurityManager all over again
by blibble 5y ago
sounds like java's SecurityManager all over again
- samus 5y agoJava's security manager blocks access to existing APIs that are already linked. The new approach relies on explicitly making only specific APIs available.
- colordrops 5y agoExcept you can run JS and C++ in it and the VM is already on every machine on earth.
- kaba0 5y agoWhich GraalVM can do much better as well, even optimizing through language boundaries (it can effectively inline a C FFI call into whatever language made that)
- emteycz 5y agoMy work computer has no GraalVM but it has two Wasm runtimes without needing to consult the IT department. Graal is cool tech but it's not playing the same game Wasm is.
- kaba0 5y agoHow is that relevant? Like, if there is a need for it than the IT department will install Graal. Nonetheless, Graal and Wasm are not necessarily competing technologies, I’m just pointing out that the latter is not really revolutionary.
- emteycz 5y agoThe point is, I think there will almost never be a need to install Graal when there is Wasm already present and used by most apps. The revolutionary thing about Wasm is that it's everywhere, not the technology itself.
- asddubs 5y agoor like bsds pledge
- naasking 5y agoNothing could be further than the truth. Capability-secure Java code just looks like Java with no surprises. The only difference is that ambient authority has been removed, which means that no code can just call new File("some_file.txt") and amplify a string that conveys no permissions into a file object conveying loads of permissions, you have to be explicitly given a Directory object that already conveys permission to a specific directory, and on which you call directory.createFile("some_file.txt") Just remove the rights amplification anti-pattern and programs instantly become more secure.