Re:TIO: Try it online
by zepolen on Saturday July 15, 2017 @01:42PM
(#14777871)
[ Parent
| on HN ]
Just because /etc/passwd can be read doesn't mean there is no sandboxing - it's just not too restrictive, probably to allow many programming languages to run (bash is one of languages after all - so process execution has to be allowed). Just having access to /etc/passwd doesn't mean the service is hacked. Check other tools like this like ideone, they allow you to read /etc/passwd as well.
Try running `ps aux` for instance and notice that you can only notice runner's processes. Try writing a file in your home, and notice that it doesn't persist between runs. Run a process in background, it doesn't stay running. Essentially every change to the runner (account on which scripts are running) is undone after provided script is done running.
Re:TIO: Try it online
by TryItOnline on Monday July 17, 2017 @03:57PM
(#14791832)
Some interpreters absolutely require being able to read /etc/passwd, as they use it to determine the user's home directory for some reason.
Since /etc/passwd, despite what the name suggests, doesn't actually contain sensitive information, I don't consider this an issue.
Just a comment overall, I bookmarked the site and think it's great.
Is it a good idea to present a site that compiles and runs code on a remote server to a site dedicated to hackers? :)
This was my first thought: sandboxing is gonna be tricky for such project.
Not really, with SELinux, which is what TIO uses. TIO can be deployed pretty much anywhere SEL is supported. Instructions here: https://github.com/TryItOnline/tiosetup