[Mailman-Developers] GSoC Updates

[Abhilash Raj]

Hi all,

After midterm evaluations I have been working on signing the message
using one the keys associated with the list, now since `python-gnupg`
does not allow selecting keys with key credentials( like address or
list-name name) so we need key_id. As barry suggested we can create a
mapping of address to key_ids and store in a seperate table.

I was of the opinion that we need key_ids only for signing the content
and hence need to select only list's keys and not user, so can we add a
new column `key_id` to the existing list table? So that the key_id is
easily accessible as a list parameter and can be easily updated. One
point in this would be should we allow more than one key associated with
a user( or address? ).
Any comments on this? (barry?)

Also I understand that keeping key safe is one of the important tasks
but for the time-being I am simply adding the public and secret keyrings
in "VAR_DIR/gpg/", all the list's private keys are in `secring.gpg` and
all the list's public keys are in `pubring.gpg` and all the user's
public keys are in `userring.gpg`. It will be changed to keep the secret
keys at a more safer location.

---
Abhilash Raj