Mercurial > docs > master

comparison discussion.roff @ 166:f102dcc06bb9

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
s/digital cryptography/signing and encryption/
author markus schnalke <meillo@marmaro.de>
date Tue, 10 Jul 2012 09:58:30 +0200
parents ea6eec1722d1
children 277eeb5ba223
comparison
equal deleted inserted replaced
165:ea6eec1722d1 166:f102dcc06bb9
1767 header field was introduced by RFC\|1864. 1767 header field was introduced by RFC\|1864.
1768 It provides detection of data corruption during the transfer. 1768 It provides detection of data corruption during the transfer.
1769 But it can not ensure verbatim end-to-end delivery of the contents 1769 But it can not ensure verbatim end-to-end delivery of the contents
1770 [RFC\|1864]. 1770 [RFC\|1864].
1771 The proper approach to verify content integrity in an 1771 The proper approach to verify content integrity in an
1772 end-to-end relationship is the use of digital cryptography. 1772 end-to-end relationship is the use of digital signatures.
1773 .\" XXX (RFCs FIXME). 1773 .\" XXX (RFCs FIXME).
1774 On the other hand, transfer protocols should detect corruption during 1774 On the other hand, transfer protocols should detect corruption during
1775 the transmission. 1775 the transmission.
1776 The TCP includes a checksum field therefore. 1776 The TCP includes a checksum field therefore.
1777 These two approaches in combinations render the 1777 These two approaches in combinations render the
2339 2339
2340 .. 2340 ..
2341 2341
2342 2342
2343 2343
2344 .H2 "Digital Cryptography 2344 .H2 "Signing and Encrypting
2345 .P 2345 .P
2346 Nmh offers no direct support for digital cryptography, 2346 Nmh offers no direct support for digital signatures and message encryption.
2347 i.e. digital signatures and message encryption.
2348 This functionality needed to be added through third-party software. 2347 This functionality needed to be added through third-party software.
2349 In mmh, the functionality should be included because digital 2348 In mmh, the functionality should be included because it
2350 cryptography is a part of modern email and likely used by users of mmh. 2349 is a part of modern email and likely wanted by users of mmh.
2351 A fresh mmh installation should support signing and encrypting 2350 A fresh mmh installation should support signing and encrypting
2352 out-of-the-box. 2351 out-of-the-box.
2353 Therefore, Neil Rickert's 2352 Therefore, Neil Rickert's
2354 .Pn mhsign 2353 .Pn mhsign
2355 and 2354 and