aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--CHANGELOG4
-rw-r--r--README25
2 files changed, 21 insertions, 8 deletions
diff --git a/CHANGELOG b/CHANGELOG
index b271b2b..8fccd8a 100644
--- a/CHANGELOG
+++ b/CHANGELOG
@@ -1,6 +1,10 @@
Firma CHANGELOG
---------------
+07/05/2012 - 0.3-git - rhatto
+
+ - Misc updates to keep firma running on newer systems.
+
08/08/2007 - 0.3-cvs (rev 1.176) - luis
- Message replay protection wasn't working at all. Fixed.
diff --git a/README b/README
index 7dbd751..2ead33c 100644
--- a/README
+++ b/README
@@ -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