project:secure_remailer:start
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
project:secure_remailer:start [2017/06/05 19:30] – [Old idea] ruza | project:secure_remailer:start [2017/06/06 16:48] (current) – [Solutions] ruza | ||
---|---|---|---|
Line 52: | Line 52: | ||
* email should be dropped, rejected or delivered (and stored in the archive) untouched | * email should be dropped, rejected or delivered (and stored in the archive) untouched | ||
- | = Mailing list archive = | + | == Mailing list archive |
Emails are stored in the email archive in a decrypted form. Since there is no requirement to reencrypt emails to the specific recepients an email archive is the only reason to hold private subkey on the receiving server. | Emails are stored in the email archive in a decrypted form. Since there is no requirement to reencrypt emails to the specific recepients an email archive is the only reason to hold private subkey on the receiving server. | ||
Line 63: | Line 63: | ||
Recipient always receives an mailing list processed emails in the form of GnuPG encrypted email and using private subkey to decrypt such email. | Recipient always receives an mailing list processed emails in the form of GnuPG encrypted email and using private subkey to decrypt such email. | ||
+ | |||
+ | As we know in our situation (brmlab council mailing list) consist of: | ||
+ | * council members | ||
+ | * brmlab members interested in council activities | ||
== Master keypair owners == | == Master keypair owners == | ||
Line 70: | Line 74: | ||
* __public subkey distribution__ on **email sender** site - since subkey is generated with one year validity (technically 12-15 months) an email clients needs to refresh to currently valid keyring state at least once a year. | * __public subkey distribution__ on **email sender** site - since subkey is generated with one year validity (technically 12-15 months) an email clients needs to refresh to currently valid keyring state at least once a year. | ||
* __private subkey distribution__ on **email recipients** site - each time new subkey generated (Usually related to the list of newly elected board members) this new subkey needs to be distributed to board members | * __private subkey distribution__ on **email recipients** site - each time new subkey generated (Usually related to the list of newly elected board members) this new subkey needs to be distributed to board members | ||
- | * Afaik in GnuPG there is no way how to generate | + | * Using [[wp>GnuPG]] expert mode there is possibility |
project/secure_remailer/start.txt · Last modified: 2017/06/06 16:48 by ruza