From 1d26f1ac74c277ceda1e4b792737dfae7e134339 Mon Sep 17 00:00:00 2001 From: daira <> Date: Mon, 29 Jul 2013 10:30:50 +0000 Subject: [PATCH] Thinko [Imported from Trac: page FAQ, version 98] --- FAQ.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/FAQ.md b/FAQ.md index e53046d..4d1fa16 100644 --- a/FAQ.md +++ b/FAQ.md @@ -24,7 +24,7 @@ The default Tahoe-LAFS parameters are `3-of-10`, so the data is spread over 10 d Erasure coding should not be confused with "secret sharing", which has the additional security property that fewer than `K` servers cannot recover any information about the data. Tahoe-LAFS' erasure coding does not have this property, and does not need to have it because we rely on secret-key encryption (using a key in the read cap) for confidentiality. -"Information Dispersal Code" (IDA) can refer either to an erasure code or a secret sharing algorithm depending on context, so we prefer not to use that term. +"Information Dispersal Algorithm" (IDA) can refer either to an erasure code or a secret sharing algorithm depending on context, so we prefer not to use that term. **Q3: Is there a way to disable the encryption for content which isn't secret? Won't that save a lot of CPU cycles?**