tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

Thinko 

[Imported from Trac: page FAQ, version 98]
daira 2013-07-29 10:30:50 +00:00
parent 284d7c99da
commit 1d26f1ac74
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
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. 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.
**<a name="Q3_disable_encryption">Q3:</a> Is there a way to disable the encryption for content which isn't secret? Won't that save a lot of CPU cycles?** **<a name="Q3_disable_encryption">Q3:</a> Is there a way to disable the encryption for content which isn't secret? Won't that save a lot of CPU cycles?**