Red Hat Bugzilla – Bug 183613
suexec module follows symlinks then realpath's them then complains because they aren't where the symlink is
Last modified: 2007-11-30 17:11:25 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; MSIE 6.0; Windows; U; AIIEEEE!; Win98; Windows 98; en-US; Gecko masquerading as IE; should it matter?; rv:1.8b) Gecko/20050217
Description of problem:
If you configure httpd to use suexec module, and you configure a directory with "Options FollowSymLinks", then suexec follows the symlink ok but then it does a realpath() (or whatever) and then complains that the symlink target doesn't live in the "docroot".
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.create a symlink in user ~/public_html/cgi-bin dir to file in any location
2.configure httpd.conf to have above directory have "Options FollowSymLinks" and "ExecCGI"
3.Open broser and execute the cgi
Actual Results: In /var/log/suexec.log:
command not in docroot (/home/USER/REALPATH/file)
Expected Results: Should have worked properly
This behaviouuur is quite unlike the behaviouuur in non-suexec locations like /var/www/cgi-bin where followed symlinks can be anywhere outside of so-called docroot. Since a user is totally constrained as to where they can create a file with a symlink to it, it is pointless for a program like suexec to say otherwise.
This report targets the FC3 or FC4 products, which have now been EOL'd.
Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?
Reassigned because Christian Iseli should either contribute positively to this
bug report else leave it alone.
This behaviour is the intent of the suexec security model; it ensures that
directory really does lie within the userdir docroot (~/public_html). You can
always hard-link files into the public_html if you want.