(PHP 4.3.4) THIS IS DRIVING ME NUTS!
I have a website where I offer members their own bit of webspace to use and
am coding a very simple 'filemanager' that allows a user to upload, delete,
and edit text files (members, of course, will not have normal sign-on FTP
access to the site - I just limit them to their own folder space). I'm
hitting a real problem with file and directory permissions, in that it seems
I'm experiencing inconsistancies with my permissions when the user attempts
to edit these files.
One question I need answered: does the server side some how keep track of
'who' originally created a file or folder ('owner', 'group', 'other'), so
that there would be a difference in later trying to apply a script-coded
CHMOD or file-open (script-coded would be 'other'-activity) on a file
originally uploaded by sign-on FTP ('owner'-created)??? In other words, if
I log on through FTP and upload a file, it has 644 permissions which allow
writes only for the 'owner' of that file. When someone is running my simple
script, that someone is seen as 'other' (?) and therefore does not have
write permissions and will not be allowed to edit the file. However, if
someone uploads a file through my simple script, again the file gets 644
permissions but now the 'owner' of the file is not an FTP sign-on user, but
some 'other' (less exalted) user. Thus when this same someone is then trying
to edit the file via my simple script, he IS permitted to do so since the 6
in the same 644 permissions now applies to him, since an 'other' was the
creator (thus 'owner') of the file. ??????????????? ?? ARGH!!!
I seem to be getting quite maddening inconsistancies in testing this out. If
any one can tell me some simple facts about how's the best way to do this
(allow general users of my site to manage their own little webspace), I
would be forever in their debt...
-dg
I have a website where I offer members their own bit of webspace to use and
am coding a very simple 'filemanager' that allows a user to upload, delete,
and edit text files (members, of course, will not have normal sign-on FTP
access to the site - I just limit them to their own folder space). I'm
hitting a real problem with file and directory permissions, in that it seems
I'm experiencing inconsistancies with my permissions when the user attempts
to edit these files.
One question I need answered: does the server side some how keep track of
'who' originally created a file or folder ('owner', 'group', 'other'), so
that there would be a difference in later trying to apply a script-coded
CHMOD or file-open (script-coded would be 'other'-activity) on a file
originally uploaded by sign-on FTP ('owner'-created)??? In other words, if
I log on through FTP and upload a file, it has 644 permissions which allow
writes only for the 'owner' of that file. When someone is running my simple
script, that someone is seen as 'other' (?) and therefore does not have
write permissions and will not be allowed to edit the file. However, if
someone uploads a file through my simple script, again the file gets 644
permissions but now the 'owner' of the file is not an FTP sign-on user, but
some 'other' (less exalted) user. Thus when this same someone is then trying
to edit the file via my simple script, he IS permitted to do so since the 6
in the same 644 permissions now applies to him, since an 'other' was the
creator (thus 'owner') of the file. ??????????????? ?? ARGH!!!
I seem to be getting quite maddening inconsistancies in testing this out. If
any one can tell me some simple facts about how's the best way to do this
(allow general users of my site to manage their own little webspace), I
would be forever in their debt...
-dg
Comment