Menu
Community /Pin to ProfileBookmark
@NogDogOct 05.2004 — #PHP normally runs as its own user (e.g.: "nobody"). I believe you can only do a chown on a file you own, or as the root "superuser". You may be able to get around this by changing the owner of the PHP file itself to that of the files to be changed (or to root) and set its permissions to include suid ("chmod 4755 file_name.php"). Just make sure you've taken into consideration what could happen if someone (either malicious or accident-prone) executes your script in such a configuration. @NogDogOct 05.2004 — #"Superuser" pretty much means what it sounds like: a user who can do anything. Normally on Unix/Linux systems this is only the "root" user account.
Anyway, if I were doing what I understand from your description, I probably would not bother with using the operating system file ownership stuff (again, based on my current understanding and subject to change without notice ? ). Instead, I would create a datbase table that for each file would have pertinent info such as file name, file owner, date uploaded, etc. Then I would use database queries to add and modify those records as needed.
Then, as an example, if a user wanted to do something to a file which you've deemed can only be done by the file "owner", you could query the database to see if the current user is the file's owner, then proceed accordingly. (Additionally, you might have a user table, and certain users - such as yourself? - might have an "admin" role that lets you override the file ownership restriction.)
prob using CHOWN… help.
I’m using chown, with a genuine user set up on the linux server. However, my script returns the rather useless error message ‘operation not permitted’. The target file has sufficient permissions also. It’s not having trouble finding the UID, just setting the chown. Any offers?
Thanks in advance.
Sign in
to post a comment5 Comments(s) ↴
0
@NogDogOct 05.2004 — #0
@NogDogOct 05.2004 — #"Superuser" pretty much means what it sounds like: a user who can do anything. Normally on Unix/Linux systems this is only the "root" user account.Anyway, if I were doing what I understand from your description, I probably would not bother with using the operating system file ownership stuff (again, based on my current understanding and subject to change without notice ? ). Instead, I would create a datbase table that for each file would have pertinent info such as file name, file owner, date uploaded, etc. Then I would use database queries to add and modify those records as needed.
Then, as an example, if a user wanted to do something to a file which you've deemed can only be done by the file "owner", you could query the database to see if the current user is the file's owner, then proceed accordingly. (Additionally, you might have a user table, and certain users - such as yourself? - might have an "admin" role that lets you override the file ownership restriction.)