Changes between Version 4 and Version 5 of AnnouncerPlugin/MessageEncryption


Ignore:
Timestamp:
Mar 8, 2010, 8:39:09 PM (14 years ago)
Author:
Steffen Hoffmann
Comment:

added link to ticket

Legend:

Unmodified
Added
Removed
Modified
  • AnnouncerPlugin/MessageEncryption

    v4 v5  
    11= Messages encryption =
    2 I'll document the effort to add support for optionally message encryption using GnuPG.
     2I'll document the effort to add support for optionally message encryption using GnuPG. See #6773 for the corresponding ticket asking for this enhancement.
    33
    44== Code structure ==
     
    1818 
    1919}}}
    20 --> Here I'll add some code to make encryption just work (1st step). Encryption/signing key ID hard-coded, growing number of variables I'd like to see as options in [annoucer] section of trac.ini and other ugliness. This will evolve over time.
     20--> Here I'll add some code to make encryption just work (1st step). Encryption/signing key ID hard-coded, growing number of variables I'd like to see as options in [annoucer] section of trac.ini and other ugliness. This will evolve over time, i.e. code will be moved out into a separate python script file and it's function will be imported into mail.py.
    2121
    2222[FIXME: add more Q+A here to help with code design evaluation and code review] 
     
    4141  * PRO: no additional dependencies but pure Python, works on Windows as well as Unix/Linux, most complete set of gpg actions including key generation and management, active development - python 3 support since July 2009, latest release v0.2.4 from 01-03-2010
    4242  * CON: no Debian package?
     43  * '''TEST''': download and local install without issues, function list_keys() ~~doesn't "just work"~~ works on a known-good gpg keyfile directory - got it, beware: "gnupghome" directory will be created silently (including parents), if something is not there exactly as specified, will have to safe-guard against creation of unwanted directories by (worst case: repeated) mis-configuration
    4344 * [http://py-gnupg.sourceforge.net/ Python GnuPGInterface]
    4445  * PRO: Debian package python-gnupginterface-0.3.2-9
     
    5657  * PRO: interface to a range of plug-in encryption modules, not only but including gnupg, language bindings for C / C++, C# / .NET, Delphi, Java, Python, and Visual Basic, re-entrant and completely thread-safe, most core algorithms implemented in assembly language, support crypto hardware acceleration facilities like in Via C3 CPU family, extensive documentation designed for cut-n-paste directly from manual
    5758  * CON: no Debian package?
    58 conclusion: test '''!PyMe''', PyGPGME, have a closer look at python-gnupg (hm, maybe), skip GnuPGInterface, OpenPGP, cryptlib (for now)[[BR]]
     59conclusion: test '''python-gnupg''', !PyMe, PyGPGME, skip GnuPGInterface, OpenPGP, cryptlib (for now)[[BR]]
    5960hints, recommendations? known-good code references or popular applications?
    6061