3 ms·
how do you handle component sandboxing in Servo compared to firefox e10s? (firefox being child process sandbox, ipc to parent, and things being a little "unperf
by zobzu 12y ago
how do you handle component sandboxing in Servo compared to firefox e10s? (firefox being child process sandbox, ipc to parent, and things being a little "unperfect" in the separation)
- pcwalton 12y agoThe plan is to use gaol [1] for sandboxing. For IPC, we want to send Rust objects serialized via serde [2] over native OS IPC pipes (AF_UNIX sockets on Unix). [1]: https://github.com/pcwalton/gaol https://github.com/pcwalton/gaol [2]: https://github.com/serde-rs/serde https://github.com/serde-rs/serde
- zobzu 12y agothat looks nice i hope the separation between processes themselves will be nicer than firefox (or even chrome) since its "from scratch" :) (ie that it wont be remoting everything and only protect the system from escaping a child - makes sense in firefox/chrome, less with rust being the compiler i guess) I suspect that if servo doesnt try to be an OS like firefox/chrome do, a whole process sandbox may even be fine enough. But if it does.. :)