News for hackers. Stuff that matters.
Re:Phpfog "Down for maintenance" by sriramk on Sunday March 20, 2011 @04:43AM (#2345855)
Heroku has done it reasonably well too and they seem to do it only with POSIX permissions for the most part.
Re:Phpfog "Down for maintenance" by moe on Sunday March 20, 2011 @07:45AM (#2346053)
Ahem. There have been multiple exploits for heroku, some of which enabled access to code and data of other heroku customers (google for "heroku vulnerability").

From what I read about their virtualization (which may not be up-to-date) they seem to rely on the security of chroot(). If that is still the case then there is a big problem in their future.

Re:Phpfog "Down for maintenance" by sriramk on Sunday March 20, 2011 @08:32AM (#2346112)
Could you expand on the last sentence? Why is relying on chroot+file permissions inherently bad?
Re:Phpfog "Down for maintenance" by baq on Sunday March 20, 2011 @08:59AM (#2346155)
chroot has not been designed as a security feature but as a system testing tool. you only need a local root exploit to get out of chroot. you need additional protection to have a proper jail; freebsd does this, openbsd used to, not sure how it is now.
Re:Phpfog "Down for maintenance" by X-Istence on Sunday March 20, 2011 @04:49AM (#2345867)
That is definitely interesting, although for Ruby that is slightly simpler because there is no real way like PHP to have a single instance of Ruby deal with all of the requests (talking about mod_php and PHP-fastcgi, not php-cgi which spawns a process per request).