Out-of-order install instructions (permissions)

Bug #266398 reported by Dr2chase
2
Affects Status Importance Assigned to Milestone
GNU Mailman
Fix Released
Medium
Unassigned

Bug Description

Quoting:

   Warning: You want to be very sure
   that the user id under which your
   CGI scripts run is not in the
   mailman group you created above,
   otherwise private archives will
   be accessible to anyone.

Problem #1: this is the first point in the
install instructions where this is so clearly
stated, far after the configure and make steps.
Yeah, sure, once upon a time we were supposed
to read all the instructions first before doing
anything, but more people will install and use
the software if you just put the steps in the
right order in the documentation. Lots of other
products manage to get this right.

Problem #2: HOW IS THIS ACCOMPLISHED? This
is important, right? Why not spend a few words
on making sure people get it right?

Problem #3: This looks like exactly the sort
of boring mechanical thing that a computer is
good at. Why is the human installer being
asked to check this?

[http://sourceforge.net/tracker/index.php?func=detail&aid=1738710&group_id=103&atid=100103]

Revision history for this message
Mark Sapiro (msapiro) wrote :

Originator: NO

Problem #1 - It seems to me this is in the right place. It is under
'setting up your web server' which is where you configure the user under
which Mailman CGIs will run.

Problem #2 - Consult your web server documentation. Normally, your web
server is not running Mailman GGIs as the mailman user anyway unless you go
out of your way to make it do so.

Problem #3 - We have no idea what web server you are running or how to
find and parse its configuration file(s), so how can we check this
mechanically? We do check at run time in the CGI wrapper to be sure that
the wrapper is invoked with the group configured with --with-cgi-gid.

Revision history for this message
Sf-robot (sf-robot) wrote :

Originator: NO

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.