From: Zooko O'Whielacronx zooko@zooko.com <zooko@zooko.com>
Date: Sun, 15 Apr 2007 19:07:35 +0000 (+0530)
Subject: pyfec: add mention of sha256sum to README
X-Git-Url: https://git.rkrishnan.org/pf/content/simplejson/frontends/%22file:/index.php?a=commitdiff_plain;h=705416d1f698e80eccaaf8a2a22a850b420d159f;p=tahoe-lafs%2Fzfec.git

pyfec: add mention of sha256sum to README

darcs-hash:1e9c2546d83ccf5ea130d7623b2ba0fec6f0457b
---

diff --git a/pyfec/README.txt b/pyfec/README.txt
index e8523cf..237b006 100644
--- a/pyfec/README.txt
+++ b/pyfec/README.txt
@@ -80,10 +80,12 @@ The bin/ directory contains two Unix-style, command-line tools "fec" and
 
 Note: a Unix-style tool like "fec" does only one thing -- in this case
 erasure coding -- and leaves other tasks to other tools.  Other Unix-style
-tools that go well with "fec" include "GNU tar" for packaging up multiple
-files and directories into one bundle, "rzip" for compression, and "GNU
-Privacy Guard" for encryption.  It is important to do things in order: first
-package, then compress, then encrypt, then erasure code.
+tools that go well with fec include "GNU tar" for archiving multiple files and
+directories into one file, "rzip" for compression, "GNU Privacy Guard" for
+encryption, and "sha256sum" for integrity.  It is important to do things in
+order: first archive, then compress, then either encrypt or sha256sum, then
+erasure code.  Note that if GNU Privacy Guard is used for privacy, then it will
+also ensure integrity, so the use of sha256sum is unnecessary in that case.
 
 
  * Performance Measurements