Changes between Version 13 and Version 14 of AnnouncerPlugin/MessageEncryption

Timestamp:

Mar 20, 2010, 8:41:45 PM (14 years ago)

Author:

Steffen Hoffmann

Comment:

added note regarding GnuPG2 and hints about options for encryption stuff

AnnouncerPlugin/MessageEncryption

@@ -8 +8 @@
 My initial assumption that I could add cryptographically functions right before inserting recipient addresses to the message was wrong.
 
-It might help a lot to look at [wiki:AnnouncerPlugin/Documentation internal structure and event flow] of AnnouncerPlugin in detail. 
+It might help a lot to look at [t:wiki:TracDev/Announcer internal structure and event flow] of AnnouncerPlugin in detail. 
 By now I add the following into code of ./announcerplugin_trunk/announcer/distributors/mail.py from trunk of AnnouncerPlugin:
 
@@ -127 +127 @@
   b. consider invention of a new class, i.e. to allow for reusable code, gpg interface initialization before sign and encrypt actions would profit among others
   c. add a minimal set of new options to [annoucer] section of trac.ini and replace formerly fixed values to gain planned control about new cryptographic functions
+   c.1 mandatory options (not needed for basic operation with common GnuPG installation
+
+   ||option name ||default value ||note ||
+   ||encrypt ||False ||whole e-mail sign/encrpt disabled, if not set to 'True', to allow smooth upgrading of existing installations ||
+
+   c.2 additional options
+
+   ||option name ||default value ||note ||
+   ||gpg_binary ||gpg ||full path to binary, needed i.e. for custom GnuPG install or GnuPG v2 ||
+    
  3. step: extend web_ui of AnnouncerPlugin to remote-control new options from user and/or administration settings
 
@@ -143 +153 @@
  ?: What are the explicitly handled exceptions?
   A: For readability let's try to put this into a table.
+
   ||exception ||cause ||action/behavior ||
   ||missing pubkey ||fingerprint in user settings but no corresponding key in pubkeyring file ||delete recipient from recipient list of event in delivery, create new event with info "specified pubkey not in Tracs keyring" to be sent to this user and project admin ||
+
+ ?: Does python-gnupg support GnuPG v2?
+  A: AFAIK yes, and I'll continue to test with both versions in the future to maintain compatibility. There might be even a bonus from using GnuPG v2, since it is announced to be PGP/MIME aware. However I'll still have to look into this in detail.
 
 === Sources (for ideas and code) ===