1.1 --- a/discussion.roff	Tue Jul 10 00:03:31 2012 +0200
     1.2 +++ b/discussion.roff	Tue Jul 10 09:58:30 2012 +0200
     1.3 @@ -1769,7 +1769,7 @@
     1.4  But it can not ensure verbatim end-to-end delivery of the contents
     1.5  [RFC\|1864].
     1.6  The proper approach to verify content integrity in an
     1.7 -end-to-end relationship is the use of digital cryptography.
     1.8 +end-to-end relationship is the use of digital signatures.
     1.9  .\" XXX (RFCs FIXME).
    1.10  On the other hand, transfer protocols should detect corruption during
    1.11  the transmission.
    1.12 @@ -2341,13 +2341,12 @@
    1.13  
    1.14  
    1.15  
    1.16 -.H2 "Digital Cryptography
    1.17 +.H2 "Signing and Encrypting
    1.18  .P
    1.19 -Nmh offers no direct support for digital cryptography,
    1.20 -i.e. digital signatures and message encryption.
    1.21 +Nmh offers no direct support for digital signatures and message encryption.
    1.22  This functionality needed to be added through third-party software.
    1.23 -In mmh, the functionality should be included because digital
    1.24 -cryptography is a part of modern email and likely used by users of mmh.
    1.25 +In mmh, the functionality should be included because it
    1.26 +is a part of modern email and likely wanted by users of mmh.
    1.27  A fresh mmh installation should support signing and encrypting
    1.28  out-of-the-box.
    1.29  Therefore, Neil Rickert's

     2.1 --- a/intro.roff	Tue Jul 10 00:03:31 2012 +0200
     2.2 +++ b/intro.roff	Tue Jul 10 09:58:30 2012 +0200
     2.3 @@ -341,7 +341,7 @@
     2.4  productivity by scripting the mail system.
     2.5  .\" XXX Naturally, he uses ...
     2.6  They naturally use modern email features, such as attachments,
     2.7 -non-ASCII text, and digital cryptography.
     2.8 +non-ASCII text, digital signatures and message encryption.
     2.9  They are able to setup email system components besides mmh,
    2.10  and actually like to have the choice to pick the ones they prefer.
    2.11  They have a reasonably modern operating system that complies to the

     3.1 --- a/summary.roff	Tue Jul 10 00:03:31 2012 +0200
     3.2 +++ b/summary.roff	Tue Jul 10 09:58:30 2012 +0200
     3.3 @@ -86,6 +86,7 @@
     3.4  Hence, experience warns that the probability for subtle bugs lurking
     3.5  in the code base is high.
     3.6  Nmh's test framework should be adjusted to mmh and extended.
     3.7 +.\" XXX path notation; signing and encrypting
     3.8  
     3.9  
    3.10  .U2 "Relationship to nmh