Mercurial > p > roundup > code
diff roundup/configuration.py @ 3922:586679a314f7
role checking for PGP mail and docs
Erik's suggestion to allow the admin to specify a set of roles to
perform PGP processing on seemed like a reasonable one I implemented
it. There is a new config option to control it.
I also realized that the signature verification had a slight problem:
it was simply checking for a valid, known signature before continuing
on. If another user in the keyring forged mail it was pass the PGP
check and then modify the db as the forged user. I changed the logic
to make sure that the author of the email matches the key of the
verifying signature.
As I was adding the documentation for the PGP processing I noticed
that there were several other new-ish options that didn't appear in
customizing.txt so I added them as well.
| author | Justus Pendleton <jpend@users.sourceforge.net> |
|---|---|
| date | Wed, 26 Sep 2007 03:20:21 +0000 |
| parents | 6b3919328381 |
| children | 1dd64778bc45 |
line wrap: on
line diff
--- a/roundup/configuration.py Wed Sep 26 03:07:55 2007 +0000 +++ b/roundup/configuration.py Wed Sep 26 03:20:21 2007 +0000 @@ -1,6 +1,6 @@ # Roundup Issue Tracker configuration support # -# $Id: configuration.py,v 1.48 2007-09-22 07:25:34 jpend Exp $ +# $Id: configuration.py,v 1.49 2007-09-26 03:20:21 jpend Exp $ # __docformat__ = "restructuredtext" @@ -720,6 +720,10 @@ ("pgp", ( (BooleanOption, "enable", "no", "Enable PGP processing. Requires pyme."), + (NullableOption, "roles", "", + "If specified, a comma-separated list of roles to perform\n" + "PGP processing on. If not specified, it happens for all\n" + "users."), (NullableOption, "homedir", "", "Location of PGP directory. Defaults to $HOME/.gnupg if\n" "not specified."),