-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dragon wrote: | | If I am not mistaken, I believe that there is currently a wrapper | script that handles access control to private archives but which gets | bypassed if the archive is public. The current architecture under | pipermail is that the actual archive pages themselves are just static | HTML files and the wrapper script only has the function of setting | and checking an access token in a cookie to access them if the | archive is private.
See <http://sourceforge.net/tracker/?func=detail&aid=850805&group_id=103&atid=300103> for one approach to this. - -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) iD8DBQFIRMKYVVuXXpU7hpMRAmdYAJ9wuGzMs92VhtcNJzvFFToTEwBRpQCfRMMn k+tsT22ALFo4hEXj8EiFTIc= =GN+0 -----END PGP SIGNATURE----- ------------------------------------------------------ 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
