On Tue, Apr 1, 2008 at 10:04 AM, Richard Lynch <[EMAIL PROTECTED]> wrote:
>
> PHP runs as the Apache user.
>
> chown/chmod the source files to not be writable by that user.
>
> Problem solved.
Let's not ignore phpSuExec or suhosin, which are fast-becoming
standard. If I'm not mistaken, the
On Mon, March 31, 2008 3:21 am, Hamar Gábor wrote:
> I am a new php user and I have a question, for which I couldn't find
> any
> answer.
>
> I'd like to restrict php code to access the filesystem. I'd like to
> have
> only one directory where the php code can write, create or read files,
> and an
On Mon, Mar 31, 2008 at 4:21 AM, Hamar Gábor <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I am a new php user and I have a question, for which I couldn't find any
> answer.
>
> I'd like to restrict php code to access the filesystem. I'd like to have
> only one directory where the php code can write, cr
> Thank you for the answer.
>
> I am running my site on a shared server, but I can overwrite the options
> in the php.ini file. Unfortunately php runs as my user, so changing the
> permissions to 644 doesn't work, php is still able to write anything.
>
> Gabor
>
ok.. your hosting enable the php s
Hi,
Thank you for the answer.
I am running my site on a shared server, but I can overwrite the options
in the php.ini file. Unfortunately php runs as my user, so changing the
permissions to 644 doesn't work, php is still able to write anything.
Gabor
2008. 03. 31, hétfő keltezéssel 16.51-kor p
> I'd like to restrict php code to access the filesystem. I'd like to have
> only one directory where the php code can write, create or read files,
> and an other directory hierarchy where the php codes present. I need
> this to avoid php code to rewrite other php code in case of bug and/or
> an at
6 matches
Mail list logo
