Ashley M. Kirchner wrote:
Hrm, yes, that would be a problem (I just tested it and it's indeed visible to everyone, despite the URL difference.)
Errr, I was wrong. It helps if I wasn't the one logged in, making administrative changes, and also checking on the archives at the same time. Once I used a different browser, it worked just fine (non-members and not-logged-in members can't get to the private archives.) So, that means that so far, mailman is working quite nicely within a suexec environment, with the set-gid bit removed from all the scripts that reside in /cgi-bin/. Disclaimer: I'm still not 100% sure whether removing the set-gid bits will have any adverse complications later. I'm still in the early stages of testing. So please don't quote me on it working fine under this environment.
-- W | I haven't lost my mind; it's backed up on tape somewhere. +-------------------------------------------------------------------- Ashley M. Kirchner <mailto:[EMAIL PROTECTED]> . 303.442.6410 x130 IT Director / SysAdmin / Websmith . 800.441.3873 x130 Photo Craft Laboratories, Inc. . 3550 Arapahoe Ave. #6 http://www.pcraft.com ..... . . . Boulder, CO 80303, U.S.A.
------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
