Prior to creating any file, the user would have been authenticated and an
authorize module
would have supplied the UID to be used for the request in an environment
variable. The location
of the user's files has to read by Apache so such that it can serve the
files (HTML).
The rational behind
On Wed, 29 Nov 2000, [EMAIL PROTECTED] wrote:
Any ideas about the best way to change the permissions and UID?
Create an external minimum perl script with the SUID bit set and with
root as it's owner. Use this script to change the file
permissions.
See you,
--
Godoy. [EMAIL PROTECTED]
hanging a file's UID from within an Apache module?
On Wed, 29 Nov 2000, [EMAIL PROTECTED] wrote:
Any ideas about the best way to change the permissions and UID?
Create an external minimum perl script with the SUID bit set and with
root as it's owner. Use this script to change the file
pe
I am creating a mod_perl Apache module. The last functionality that I need
to implement is the ability to set the UID of the files and directories
which are created and modified by the Apache module to something other than
Apache's child UID.
For example, if when I built Apache 1.3.14 on Linux
