This website is deprecated, and remains online only for historic access to old issues and docs for historic versions of Virtualmin. It has been unmaintained for several years, and should not be relied on for up-to-date information. Please visit www.virtualmin.com instead.
So this is what it should look like?
[code:1]<Directory ${HOME}/public_html>
Options -Indexes IncludesNOEXEC FollowSymLinks Includes
allow from all
AllowOverride All
</Directory>
<Directory ${HOME}/cgi-bin>
allow from all
</Directory>[/code:1]
So this is what it should look like?
[code:1]<Directory ${HOME}/public_html>
Options -Indexes IncludesNOEXEC FollowSymLinks Includes
allow from all
AllowOverride All
</Directory>
<Directory ${HOME}/cgi-bin>
allow from all
</Directory>[/code:1]
But essentially, "Includes" allows users to use the "exec" option, and "IncludesNOEXEC" disables the ability for users to call "exec".
It's certainly no worse than what you can do with CGI (ie, PHP, Perl, Ruby, etc), but the difference is that in your above configuration, CGI apps are only allowed to be executed from within /cgi-bin/.
It all depends on how much your trying to lock things down :-)
-Eric
Add "Includes" to the Options section of the Directory section of the Apache Server Template.
--
Check out the forum guidelines!
Oh, and this won't effect existing virtual servers (pretty much nothing in Server Templates does). You'll need to hit them up individually.
--
Check out the forum guidelines!
So this is what it should look like?
[code:1]<Directory ${HOME}/public_html>
Options -Indexes IncludesNOEXEC FollowSymLinks Includes
allow from all
AllowOverride All
</Directory>
<Directory ${HOME}/cgi-bin>
allow from all
</Directory>[/code:1]
So this is what it should look like?
[code:1]<Directory ${HOME}/public_html>
Options -Indexes IncludesNOEXEC FollowSymLinks Includes
allow from all
AllowOverride All
</Directory>
<Directory ${HOME}/cgi-bin>
allow from all
</Directory>[/code:1]
Howdy,
Well, you need to choose between "Includes" and "IncludesNOEXEC" (your example contains both).
You can read about the two here:
http://httpd.apache.org/docs/2.0/mod/mod_include.html
But essentially, "Includes" allows users to use the "exec" option, and "IncludesNOEXEC" disables the ability for users to call "exec".
It's certainly no worse than what you can do with CGI (ie, PHP, Perl, Ruby, etc), but the difference is that in your above configuration, CGI apps are only allowed to be executed from within /cgi-bin/.
It all depends on how much your trying to lock things down :-)
-Eric