diff options
| author | Silvio Rhatto <rhatto@riseup.net> | 2012-05-07 11:43:08 -0300 |
|---|---|---|
| committer | Silvio Rhatto <rhatto@riseup.net> | 2012-05-07 11:43:08 -0300 |
| commit | dd0e0c07c15e36743a043955fe5021ade92bc3d1 (patch) | |
| tree | 259e69d53effe353f7cd24f52574c7026ba018d9 /README | |
| parent | 0b327f9c96d3c7d9630c3dc3a3160009eee86e4a (diff) | |
| download | firma-dd0e0c07c15e36743a043955fe5021ade92bc3d1.tar.gz firma-dd0e0c07c15e36743a043955fe5021ade92bc3d1.tar.bz2 | |
Doc update
Diffstat (limited to 'README')
| -rw-r--r-- | README | 25 |
1 files changed, 17 insertions, 8 deletions
@@ -57,12 +57,21 @@ Everyone has the private key X The server has the private key the message to all recipients cause this has none automation in the process we are looking for. - For the first we have GPG Mailman, - http://medien.informatik.uni-ulm.de/~stefan/gpg-mailman.xhtml + For the first there are some options: - and Crypt-ML, http://www.synacklabs.net/projects/crypt-ml/ + - Schleuder + http://schleuder2.nadir.org/ - For the second option we have the NAH6 Mailman patch, + - GPG Mailman + http://medien.informatik.uni-ulm.de/~stefan/gpg-mailman.xhtml + + - Crypt-ML - gpg-ezmlm + http://www.synacklabs.net/projects/crypt-ml/ + + - Secure Email List Services (SELS) + http://sels.ncsa.illinois.edu/ + + For the second option there is the NAH6 Mailman patch, http://mail.python.org/pipermail/mailman-coders/2003-June/000506.html For the firsts releases of Firma, we choose to use just the first option. @@ -85,14 +94,14 @@ Everyone has the private key X The server has the private key public. Designing Firma, we decided for the centralized model, for three main reasons: - 1 - a server can be safer than any user's ordinary computer. + 1 - A server can be safer than any user's ordinary computer. - 2 - automation: when some user is removed from the list, we just remove their + 2 - Automation: when some user is removed from the list, we just remove their key from the list keyring; in the decentralized approach, the list admin needs to regenerate a new list keypair, otherwise the unsubscribed user can still decrypt list messages if he can sniff the mail server traffic. - 3 - use a public-key and all info stored onto it as the subscriber info. + 3 - Use a public-key and all info stored onto it as the subscriber info. Why Bash -------- @@ -291,7 +300,7 @@ Design and features (OUTDATED) encrypted message and the signature in two separate blocks. Thats a firma and not Sylpheed issue. The PGP/MIME spec allows one to send the PGP/MIME encrypted message in two separate blocks. We hope to fix - this soon :) + this someday :) 9 - Contact |