Hi,
We have been using the Approved header as a way to automtically approve
commit logs to a read-only mailinglist. We recently moved our
infrastructure to github and I wrote a patch to the github Email service
hook to add an Approved header.
https://github.com/github/github-services/pull/84
Now the problem of course is that this secret currently is either the list
admin or the list moderator password, which is far from secure. Especially
if the mails are not created on the mailman list server.
So I would propose to allow to set a separate secret used for approved
messages. If compromised, it's easy to change that secret on both sides.
Is this acceptable ?
Thanks in advance
--
-- dag wieers, d...@wieers.com, http://dag.wieers.com/
-- dagit linux solutions, i...@dagit.net, http://dagit.net/
[Any errors in spelling, tact or fact are transmission errors]
------------------------------------------------------
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
