News for hackers. Stuff that matters.
Re:Rustler is a library for writing Erlang NIFs in safe Rust... by simcop2387 on Monday September 16, 2019 @07:16PM (#20989508)
Good chance that'll start to change as WASM gets more fleshed out and more commonly used, but that is a barrier to it's adoption at the moment.
Re:Rustler is a library for writing Erlang NIFs in safe Rust... by dmix on Monday September 16, 2019 @10:35PM (#20990707)
What's stopping it exactly?
Re:Rustler is a library for writing Erlang NIFs in safe Rust... by dmix on Tuesday September 17, 2019 @03:41AM (#20992625)
Nevermind found time to research it myself, this was a good overview https://github.com/WebAssembly/content-security-policy/blob/...
Re:Rustler is a library for writing Erlang NIFs in safe Rust... by namibj on Tuesday September 17, 2019 @07:05AM (#20993631)
Chrome restricts it to unsafe-eval CSP. The main risk described seems to be escaping to the global object. Can't we use the power of a tracing GC to determine whether the global object is reachable from the import object, and put _that_ under unsafe-eval? Or add descriptions/tags that need to explicitly allow dangerous APIs to be reachable by the import object, and refuse if any undeclared dangerous APIs are reachable with a CSP not containing unsafe-eval?

I see both sides, but full unsafe-eval is too much of a wrecking ball when a warded lock[0] on this proverbial door to the WASM kingdom would be sufficient.

[0]: https://en.wikipedia.org/wiki/Warded_lock

Re:Rustler is a library for writing Erlang NIFs in safe Rust... by hackcasual on Tuesday September 17, 2019 @12:59PM (#20997414)
Both FireFox and Safari support same origin CSP on instantiateStreaming sources though, which doesn't work on Chrome.
Re:Rustler is a library for writing Erlang NIFs in safe Rust... by namibj on Thursday September 26, 2019 @07:41AM (#21079992)
I actually mean even harsher restrictions than just some same-origin. Specifically, I mean using already-existing mechanics to figure out whether the global object is reachable by the WASM code. If so, treat as unsafe-eval for all I care. If not, treat as risky as the functionality exposed to the WASM code (testing reachability for other objects/functions that are not the global object itself).