summaryrefslogtreecommitdiff
path: root/po
diff options
context:
space:
mode:
authorEduardo Chappa <chappa@washington.edu>2014-05-02 19:04:29 -0600
committerEduardo Chappa <chappa@washington.edu>2014-05-02 19:04:29 -0600
commit223b392e8d40a0622936403d1da5eaf0cdd54d60 (patch)
tree05858ceae7dea53c9e97c205ce524a112f41723e /po
parent0d1e49834f4c3005b2b92a4ce8a03bd395d2fb1e (diff)
downloadalpine-223b392e8d40a0622936403d1da5eaf0cdd54d60.tar.xz
* Create help for explaining how encrypted password file support
works. * When a message is sent encrypted, add the sender certificate so that the sender can decrypt it too. * When a message is signed and encrypted, first sign it and then encrypt it. This changes the usual order of encrypting and then signing, and it has the shortcoming of making bigger messages. However, this is the way that most clients work with S/MIME, and so for compatibility with other programs, we will send signed, then encrypted, instead of encrypted, then signed. Hmm... should we sign the encrypted part? * Avoid the first RSET smtp command, as this causes delays in some evily managed servers.
Diffstat (limited to 'po')
-rw-r--r--po/Makefile.in2
1 files changed, 1 insertions, 1 deletions
diff --git a/po/Makefile.in b/po/Makefile.in
index 0f400a1..cc1c5ab 100644
--- a/po/Makefile.in
+++ b/po/Makefile.in
@@ -11,7 +11,7 @@
# Origin: gettext-0.16
PACKAGE = alpine
-VERSION = 2.19.99
+VERSION = 2.19.991
PACKAGE_BUGREPORT = chappa@washington.edu
SHELL = /bin/sh