Optionally encrypt messages using GnuPG

[Steffen Hoffmann]

Messages may contain sensitive information that may be not allowed to traverse over insecure channels (Internet) in corporate Trac applications, support to

• encrypt to all recipients
• send both encrypted and unencrypted messages

should be as easy _and_ flexible as possible, i.e. choosing public keys based on recipients list (warn/report, if not all corresponding keys could be found) more ...

[Steffen Hoffmann]

Maybe this sounds like a big task, but the good news is, I already started coding this, however someone contributing or/and giving hints about implementation of python gpg functions is always welcome :-)

[Robert Corsaro]

If there is anything you need on my side, ask away. Whether it be a branch, some explaining of announcer, direction, code reviews. You may want to checkout dokipen on github if you like git (like I do!). I'm usually idling in #trac, just ping me if you want to chat.

[anonymous]

Replying to doki_pen:

If there is anything you need on my side, ask away. Whether it be a branch, some explaining of announcer, direction, code reviews. You may want to checkout dokipen on github if you like git (like I do!). I'm usually idling in #trac, just ping me if you want to chat.

Thanks for taking care. I'll ask for code review once I have code at least working up to some degree. I'd prefer to set names and needed structure extensions in agreement with good python coding style and even ours, since I'd prefer a clean implementation and inclusion into trunk over an personal freestyle. For sure I've to learn a lot here.

[Steffen Hoffmann]

Feel free to follow (and comment) on AnnouncerPlugin/MessageEncryption for ideas and discussion.

[Steffen Hoffmann]

Testing working code since 10-03-2010, implementing only encrypt function, no recipient separation and other needed features (from my point of view), so not ready for an initial public disclosure here.

I want to improve a bit on my own, but will make use of kind offer for code review soon - thanks.

[Steffen Hoffmann]

This is WiP now and a preliminary version was added to trunk with changeset [8087]. There is support for multiple keys/user, arbitrary cryptographically operation (encrypt-only|sign-only|encrypt+sign) as well as administrative email domain limitation (doesn't allow to send to arbitrary email addresses, send unencrypted mail only to certain domain(s)).

A functionally reduced version inspired by the work here was even suggested for Trac (see ​Trac #8294) and might be implemented in Trac first, depending on the speed of development in branch for Announcer integration into Trac (see ​proposal). Please test and help to improve this, if you're interested.