Re: Help with windows 2003 iis6, exec() and permissions
| From: | Adam Niedzwiedzki | Date: | Thu, 19 May 2005 05:43:53 +0000 |
| Subject: | Re: Help with windows 2003 iis6, exec() and permissions | ||
| References: | 1 2 | Groups: | php.windows |
| Request: | Send a blank email to php-windows+get-26032@lists.php.net to get a copy of this message | ||
Hi Louis,
So is that just the case of adding IUSER_XXX to cmd.exe?
What permissions do I give IUSER on cmd.exe?
Isn't that a big risk? Is there a way to exploit that? (apart from someone
uploading php code etc), via a URL or something?
Just wanting the "correct/safest" way to do this.
Cheers
Adam
"Louis Solomon" <php-louis@steelbytes.com> wrote in message
news:20050519013707.30426.qmail@lists.php.net...
>> What is the correct way to setup php/iis to allow php access to run
>> exec() (ping.exe,cat.exe (from gnu utilities for win32), and any other
>> command shell stuff.) etc.
>
> access to %windir%\system32\cmd.exe is required. this is denied in a
> default IIS6 installation.
>
> --
> Louis Solomon
> www.SteelBytes.com
>
> "Adam Niedzwiedzki" <adstar@genis-x.com> wrote in message
> news:20050518221257.31314.qmail@lists.php.net...
>> Hi all,
>>
>> There is so much info on google/pnp.net etc on this but all of them seem
>> to work some of the time and the rest of them seem to work the rest of
>> the time;).
>>
>> I just can't seem to find what is the most secure and correct/guaranteed
>> way of setting this up.
>>
>> A windows 2003 server, running IIS6, and PHP 4.3.11, soon to move to php
>> 5.0.4.
>> What is the correct way to setup php/iis to allow php access to run
>> exec() (ping.exe,cat.exe (from gnu utilities for win32), and any other
>> command shell stuff.) etc.
>> Also what is the correct way to setup folder permissions on Windows 2003
>> to allow php to write a file. Is it possible to set permissions on the
>> folder and not the file (in case it has the file is deleted and uploaded
>> again etc).
>>
>> I've googled and found 1000's, 10's of 1000's of options but after
>> working through the first half dozen and not having any luck (or most of
>> the saying that you open your system up to a HUGE security hole if you
>> give IUSER_XXX write access to cmd.exe, I'm just after the
>> "correct"/recommended" way to do the above.
>>
>> Cheers
>> Adam
>>