4 ms·
"What exactly do you mean by [the playground is restricted]?" The Playground is a very special build of Go. I don't even think it's open sourced, often because
by jerf 10y ago
"What exactly do you mean by [the playground is restricted]?"
The Playground is a very special build of Go. I don't even think it's open sourced, often because while you can't depend on security-by-obscurity you still don't necessarily want to just hand people the source to attack on their own. It's written to prevent people from abusing the playground, so for instance, the os package can't read real files, the time package returns constants for "time.Now()" rather than using the clock, and an arbitrary number of other changes are made to prevent abuse. How many changes it is I don't know exactly, but there's certainly a number of them. But, more importantly, the QA work for such a thing is quite substantial. Many of the changes would also preclude using the playground to investigate the new features; for instance, you can't test HTTP2 support on there since you can't open sockets or servers. Presumably updating it would require significant effort, and at the very least, it can't be afforded to make that a blocker for a release.
- arjovr 10y agohttps://github.com/golang/playground https://github.com/golang/playground
- jerf 10y agoThank you, I stand corrected.
- maddyboo 10y agoOh interesting, I didn't realize it was a very special build of Go itself. I did know it was restricted, I guess I just underestimated how difficult that is to do. I didn't think the restrictions were actually implemented in the Go source, I thought it was more a locked down container plus a few restrictions implemented externally in the Playground's server code. It would be cool to know more about this, maybe I'll take a look at the source as @arjovr linked. Thanks!
- Merovius 10y ago> Oh interesting, I didn't realize it was a very special build of Go itself. It's not. It uses NaCl (native client), but that's just a special GOOS/GOARCH pair with a supporting runtime. NaCl is what the chrome sandbox is based upon, it's cool technology :) > It would be cool to know more about this, maybe I'll take a look at the source as @arjovr linked. You can also start here: https://blog.golang.org/playground https://blog.golang.org/playground
- Manishearth 10y agoInteresting. Rust has two playgrounds (official: https://play.rust-lang.org/ https://play.rust-lang.org/, unofficial: http://play.integer32.com/ http://play.integer32.com/), and each is a completely different bit of open-source software (https://github.com/rust-lang/rust-playpen https://github.com/rust-lang/rust-playpen , https://github.com/integer32llc/rust-playground https://github.com/integer32llc/rust-playground) They both use docker for isolation, with a bunch of things to make it work. IIRC we haven't had any issues with this. Furthermore, the official playground used to be a third completely different bit of software until it was rewritten in Rust. It also used to use https://github.com/thestinger/playpen https://github.com/thestinger/playpen. I'm skeptical that the problem will take that much effort since Rust has solved it (to some degree) twice. At the same time, it's likely that Go's playpen does a lot more mitigation, e.g. the time.Now() probably futzes timing attacks. Though in that case they would need to mess with mutexes or scheduling as well (since you can use shared memory to build a timer), which complicates things. (For timing attacks I still think the solution still lies in how you set up the container, specifically isolating its memory accesses -- instead of tweaking the compiler itself)
- remus 10y agoAndrew Gerrand wrote a nice overview of how the go playground works: https://blog.golang.org/playground https://blog.golang.org/playground Im pretty sure the source code is available somewhere, though usage isn't very well documented. There's periodic requests on golang-nuts about how to get your own version up and running.
- Manishearth 10y agoThanks. Looks like the reason the time functionality is restricted is to avoid DOSes and server load, not to prevent against side channel attacks (which like I said are possible anyway with mutexes and channels). The rest could be pretty easily implemented via docker or some other sandboxing method (the time stuff sort of can be handled too, but it's trickier). It might be more vulnerable to load, but it will be able to work with a pristine Go toolchain and provide options like switching between versions; much like the Rust playground.