Rust is pretty uniquely positioned to explore using things like WASM for sandboxing steps of the build which are otherwise authored in Rust, like procedural macros:https://twitter.com/jedisct1/status/1183773459651989511 …
-
-
I've got a
@rustsecurecode vaporware for thathttps://github.com/rust-secure-code/cargo-sandbox … -
As far as non-vaporware goes, `rustwide` looks like a super awesome thing to build both a sandboxing system and a build reproduction system on top of /cc
@QuietMisdreavus@pietroalbinihttps://github.com/rust-lang/rustwide …
End of conversation
New conversation -
-
-
Advocating for PNaCl?

- 2 more replies
New conversation -
-
-
We should compile the compiler to WASM for sure :) I agree that sounds mostly like theater but defense in depth is a thing?
-
Crazy idea: rustc in your browser powering
@mattgodbolt's godbolt - 3 more replies
New conversation -
-
-
(i.e. a malicious proc macro could compile evil code into the binary.)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
i do think trying to sandbox "http://build.rs " a bit would be a very interesting experiment
-
I've been very curious about http://build.rs + WASI for this /cc
@pcwalton
End of conversation
New conversation -
-
-
"reflections on boxing box"
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.
