News for hackers. Stuff that matters.
Re:A New Codecademy by zx2c4 on Wednesday April 23, 2014 @01:38PM (#7635529)
I'm interested to learn about their sandboxing. They allow a lot of user-submitted code to run server side. How do they sandbox this? What level of isolation do they use?

    - If language-runtime patches, then there are escapes likely.
    - If chroot, then there are escapes.
    - If linux namespaces, then there are escapes.
    - If ...
Which level did they go for?
Re:A New Codecademy by amasad on Wednesday April 23, 2014 @05:11PM (#7636943)
I used to work there, not sure if things changed (we've given talks and written about it in the past): Language-runtime patches + user permissions (setuid) + rlimit + Linux containers + runner boxes have no access to web server , db server etc, so even if you root, nothing much to do.
Re:A New Codecademy by zx2c4 on Wednesday April 23, 2014 @05:26PM (#7637017)
They still return code that runs javascript in the main codecademy domain, so you could potentially modify the servers to return tainted data to steal cookies and whatnot.
Re:A New Codecademy by amasad on Thursday April 24, 2014 @10:47AM (#7640579)
They don't return code that run JavaScript. All code is executed on the server and only a string of the result is returned. For web courses, evaluation is done client-side and is properly sandbox. See [1] to learn more about the client-side sandboxing.

[1] https://github.com/Codecademy/stuff.js

Re:A New Codecademy by innonate on Wednesday April 23, 2014 @03:15PM (#7636246)
Knowing you, you already know :D