From: Zooko O'Whielacronx Date: Thu, 28 May 2009 23:34:22 +0000 (-0700) Subject: docs: small edit to about.html X-Git-Tag: trac-3900~10 X-Git-Url: https://git.rkrishnan.org/listings/configuration.rst?a=commitdiff_plain;h=9a02f4a1043d62883493c6cf55bded9f7f1e7028;p=tahoe-lafs%2Ftahoe-lafs.git docs: small edit to about.html --- diff --git a/docs/about.html b/docs/about.html index 2b5bab44..c0b1cbac 100644 --- a/docs/about.html +++ b/docs/about.html @@ -16,7 +16,7 @@

(See also Tahoe-LAFS for Paranoids and Tahoe-LAFS for Corporates.)

-

A "storage grid" is made up of a number of storage servers. A storage server has local attached storage (typically one or more hard disks). A "gateway" uses the storage servers and provides a filesystem over a standard protocol such as HTTP(S), FUSE, SMB, or (S)FTP.

+

A "storage grid" is made up of a number of storage servers. A storage server has local attached storage (typically one or more hard disks). A "gateway" uses the storage servers and provides access to the filesystem over HTTP(S) or (S)FTP.

Users do not rely on storage servers to provide confidentiality nor integrity for their data -- instead all of the data is encrypted and integrity-checked by the gateway, so that the servers can neither read nor alter the contents of the files.

Users rely on storage servers for availability. The ciphertext is erasure-coded and distributed across N storage servers (the default value for N is 10) so that it can be recovered from any K of these servers (the default value of K is 3). Therefore only the simultaneous failure of N-K+1 (with the defaults, 8) servers can make the data unavailable.

In the typical deployment mode each user runs her own gateway on her own machine. This way she relies on her own machine for the confidentiality and integrity of the data.