Posted by Jim Michaels on 03/02/06 20:56

"bish" <info@bish.org> wrote in message
news:ice9v1tae3mvankafhbhbr3uj1a7ss2ord@4ax.com...
> On Thu, 16 Feb 2006 10:46:42 -0000, Jasen Betts
> <jasen@free.net.nz> wrote:
>
>>>>On 2006-02-15, bish <info@bish.org> wrote:
>>>>
>>>>> Thank you.
>>>>>
>>>>> Do you mean that if I don't put the full absolute path that anyone
>>>>> can write to the directory?
>>>>>
>>>>> When the present task is over I'll experiment with the full path
>>>>> as you suggest but, for now, I don't understand the 01777? Was
>>>>> it just a typo?
>>>>> Yoooors,
>>>>
>>>>01777 is global RWX with the sticky bit so user A can't delete user B's
>>>>files.
>>>>same as /tmp normally has.
>>>>
>>>>Bye.
>>>> Jasen
>
> <small_voice> oh </small_voice>

now I don't understand. I thought 0755 would be plenty sufficient for
mkdir.
My understanding is that you need to set umask() to 022 or at least to 0 to
get mkdir to work. I don't know what the admins are setting their umask
value at - it must be an odd duck or very very secure.
is there an ownership problem between PHP and uploading of files or
something?


why the need for the sticky bit? is someone going to come along and delete
our files? I thought that's why we have user accounts. (sorry - it's been a
while since I had a UNIX account) for 01777 the wx on global is the reason
for the need of the sticky bit, meaning since everybody can read/write our
files, and cd into our directory, then we don't want them deleting our
files?

[Back to original message]