Changes between Version 26 and Version 27 of AnnouncerPlugin/MessageEncryption

Timestamp:

May 10, 2017, 4:40:30 PM (7 years ago)

Author:

figaro

Comment:

Typo

AnnouncerPlugin/MessageEncryption

@@ -26 +26 @@
  1. Install GnuPG on the same host along with Trac[[BR]]
   For Debian GNU/Linux a simple
-{{{!#sh
-   $ apt-get install gnupg
+ {{{#!sh
+$ apt-get install gnupg
 }}}
  will do.
@@ -67 +67 @@
 
 [FIXME: add more Q+A here to help with code design evaluation and code review]  
- ?: ''Is it true that different users will have different keys?  If so, we can add configuration to the user's preference page.  We could have a big textbox for GPG key and if they have one entered, then use encryption.
-  A: Yes, different users will (typically) have different keys. It might be desirable even to support multiple keys per user. Only in rare cases one key would be associated with different users/e-mail addresses, even if this might be technically perfectly valid and useful. But it indicates violation of the de-facto standard one-owner-per-key that abhor kind of group keys. Update: User preferences will be provided by CryptoPlugin.
+ ?: Is it true that different users will have different keys? If so, we can add configuration to the user's preference page. We could have a big textbox for GPG key and if they have one entered, then use encryption.
+   A: Yes, different users will (typically) have different keys. It might be desirable even to support multiple keys per user. Only in rare cases one key would be associated with different users/e-mail addresses, even if this might be technically perfectly valid and useful. But it indicates violation of the de-facto standard one-owner-per-key that abhor kind of group keys. Update: User preferences will be provided by CryptoPlugin.
  ?: Why not implement encryption as another IAnnouncementEmailDecorator
   A: Decorators are called without guaranteed order. Encryption needs control, that it'll be the last message body mangling action.