Mercurial > p > roundup > code
comparison roundup/configuration.py @ 4541:62239a524beb
PGP support is again working (pyme API has changed significantly)...
...and we now have a regression test. We now take care that
bounce-messages for incoming encrypted mails or mails where the policy
dictates that outgoing traffic should be encrypted is actually
pgp-encrypted. Note that the new pgp encrypt option for outgoing mails
works only for bounces for now.
| author | Ralf Schlatterbeck <schlatterbeck@users.sourceforge.net> |
|---|---|
| date | Fri, 07 Oct 2011 14:21:57 +0000 |
| parents | d483a40e2f82 |
| children | d9d7319afffa |
comparison
equal
deleted
inserted
replaced
| 4540:bf67fed13ef9 | 4541:62239a524beb |
|---|---|
| 797 "parts of the multipart/alternative are ignored. The default\n" | 797 "parts of the multipart/alternative are ignored. The default\n" |
| 798 "is to keep all parts and attach them to the issue."), | 798 "is to keep all parts and attach them to the issue."), |
| 799 ), "Roundup Mail Gateway options"), | 799 ), "Roundup Mail Gateway options"), |
| 800 ("pgp", ( | 800 ("pgp", ( |
| 801 (BooleanOption, "enable", "no", | 801 (BooleanOption, "enable", "no", |
| 802 "Enable PGP processing. Requires pyme."), | 802 "Enable PGP processing. Requires pyme. If you're planning\n" |
| 803 "to send encrypted PGP mail to the tracker, you should also\n" | |
| 804 "enable the encrypt-option below, otherwise mail received\n" | |
| 805 "encrypted might be sent unencrypted to another user."), | |
| 803 (NullableOption, "roles", "", | 806 (NullableOption, "roles", "", |
| 804 "If specified, a comma-separated list of roles to perform\n" | 807 "If specified, a comma-separated list of roles to perform\n" |
| 805 "PGP processing on. If not specified, it happens for all\n" | 808 "PGP processing on. If not specified, it happens for all\n" |
| 806 "users."), | 809 "users. Note that received PGP messages (signed and/or\n" |
| 810 "encrypted) will be processed with PGP even if the user\n" | |
| 811 "doesn't have one of the PGP roles, you can use this to make\n" | |
| 812 "PGP processing completely optional by defining a role here\n" | |
| 813 "and not assigning any users to that role."), | |
| 807 (NullableOption, "homedir", "", | 814 (NullableOption, "homedir", "", |
| 808 "Location of PGP directory. Defaults to $HOME/.gnupg if\n" | 815 "Location of PGP directory. Defaults to $HOME/.gnupg if\n" |
| 809 "not specified."), | 816 "not specified."), |
| 817 (BooleanOption, "encrypt", "no", | |
| 818 "Enable PGP encryption. All outgoing mails are encrypted.\n" | |
| 819 "This requires that keys for all users (with one of the gpg\n" | |
| 820 "roles above or all users if empty) are available. Note that\n" | |
| 821 "it makes sense to educate users to also send mails encrypted\n" | |
| 822 "to the tracker, to enforce this, set 'require_incoming'\n" | |
| 823 "option below (but see the note)."), | |
| 824 (Option, "require_incoming", "signed", | |
| 825 "Require that pgp messages received by roundup are either\n" | |
| 826 "'signed', 'encrypted' or 'both'. If encryption is required\n" | |
| 827 "we do not return the message (in clear) to the user but just\n" | |
| 828 "send an informational message that the message was rejected.\n" | |
| 829 "Note that this still presents known-plaintext to an attacker\n" | |
| 830 "when the users sends the mail a second time with encryption\n" | |
| 831 "turned on."), | |
| 810 ), "OpenPGP mail processing options"), | 832 ), "OpenPGP mail processing options"), |
| 811 ("nosy", ( | 833 ("nosy", ( |
| 812 (RunDetectorOption, "messages_to_author", "no", | 834 (RunDetectorOption, "messages_to_author", "no", |
| 813 "Send nosy messages to the author of the message.", | 835 "Send nosy messages to the author of the message.", |
| 814 ["MESSAGES_TO_AUTHOR"]), | 836 ["MESSAGES_TO_AUTHOR"]), |