[php-maint] Bug#603174: Bug#603174: Why do we get just *part* of 5.3.3?
hubert depesz lubaczewski
depesz at gmail.com
Tue Dec 14 10:01:32 UTC 2010
On Mon, Dec 13, 2010 at 6:50 PM, Thomas Goirand <thomas at goirand.fr> wrote:
> This was a request from the release team that didn't want too much
> change between php 5.3.2 and the new 5.3.3.
> BTW, waking-up so late on this issue, and so close from the release of
> Squeeze, and without reading what has been already said about it, seems
> a bit ... hum ... inappropriate at least! :)
I did some googling - "php fpm debian", but didn't find any reasonable
links. Perhaps, someone knowing could/should provide link in this bug?
> If you are searching for a solution on how to do safe executions of PHP,
> by the way, I would suggest you to use SBOX. It does safe chroot,
> setlimits and setuid before executing (of course, you need a working
> environment in your chroot...). I'm currently working on a new version
> that makes it possible for sbox to find the PHP interpreter without
> having to play with binfmt_misc, and it's been already working
> experimentally. If you care, you can clone:
> I've just finished adding the support for Apache SetEnv directive, so
> that any variables in /etc/sbox.conf can be overwritten on a per-vhost
> basis. Oh, and it's also working for python and perl cgi scripts! :)
> I think the above is a way more safe than using fcgid, even though it
> might not perform as well (this would have to be benched, I'm really not
thanks will check.
http://www.depesz.com/ - nowy, lepszy depesz
More information about the pkg-php-maint