On Thursday 02 October 2008, Alexander Prinsier wrote:
> > Apart from that, allowing scripts owned by root to be executed as
> > any user would certainly create (local) security issues. Using a
> > dedicated user might be possible, though.
>
> Why would running a root-owned script as a local user c
Ondřej Surý wrote:
>> So the actual item for the wishlist is to be able to specify a user (or more
>> than one) that are considered trusted. Suexec will then allow files
>> owned by either the target user, or by a trusted user, to be executed.
>
> Use chattr +i
>
> Ondrej.
That much we had alr
> So the actual item for the wishlist is to be able to specify a user (or more
> than one) that are considered trusted. Suexec will then allow files
> owned by either the target user, or by a trusted user, to be executed.
Use chattr +i
Ondrej.
--
Ondřej Surý <[EMAIL PROTECTED]>
Stefan Fritsch wrote:
>> So the actual item for the wishlist is to be able to specify a user
>> (or more than one) that are considered trusted. Suexec will then
>> allow files owned by either the target user, or by a trusted user,
>> to be executed.
>
> First of all, have you looked at
>
> suphp
Hi,
On Wednesday 17 September 2008, Alexander Prinsier wrote:
> I'm using apache2 together with fastcgi, suexec and php. To
> configure php I'm using a wrapper script to set PHPRC, which then
> exec's php itself.
>
> I don't want users to set their own PHPRC, so they could modify the
> php.ini for
Package: apache2-suexec-custom
Severity: wishlist
I'm using apache2 together with fastcgi, suexec and php. To configure php I'm
using a wrapper script to set PHPRC, which then exec's php itself.
I don't want users to set their own PHPRC, so they could modify the php.ini for
their site. This mea
6 matches
Mail list logo