ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2025-02-07 11:50:21 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

doc: eliminate the phrase "rootcap" from doc/frontends/FTP-and-SFTP.rst

Browse Source 
Two different people have asked me for help, saying they couldn't figure out what a "rootcap" is. Hopefully just calling it a "cap" will make it easier for them to find out from the other docs what it is.
This commit is contained in:
Zooko O'Whielacronx 2011-08-09 06:26:01 -07:00
parent b60506b0ba
commit 43ba172f65
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/frontends/FTP-and-SFTP.rst
View File

@ -42,16 +42,16 @@ sit at the same level as the web-API interface.
Since Tahoe-LAFS does not use user accounts or passwords, the FTP/SFTP Since Tahoe-LAFS does not use user accounts or passwords, the FTP/SFTP
servers must be configured with a way to first authenticate a user (confirm servers must be configured with a way to first authenticate a user (confirm
that a prospective client has a legitimate claim to whatever authorities we that a prospective client has a legitimate claim to whatever authorities we
might grant a particular user), and second to decide what root directory cap might grant a particular user), and second to decide what directory cap
should be granted to the authenticated username. A username and password is should be granted to the authenticated username. A username and password is
used for this purpose. (The SFTP protocol is also capable of using client RSA used for this purpose. (The SFTP protocol is also capable of using client RSA
or DSA public keys, but this is not currently implemented.) or DSA public keys, but this is not currently implemented.)
Tahoe-LAFS provides two mechanisms to perform this user-to-rootcap Tahoe-LAFS provides two mechanisms to perform this user-to-cap mapping. The
mapping. The first is a simple flat file with one account per line. The first is a simple flat file with one account per line. The second is an
second is an HTTP-based login mechanism, backed by simple PHP script and a HTTP-based login mechanism, backed by simple PHP script and a database. The
database. The latter form is used by allmydata.com to provide secure access latter form is used by allmydata.com to provide secure access to customer
to customer rootcaps. caps.
Creating an Account File Creating an Account File
======================== ========================
@ -61,7 +61,7 @@ BASEDIR/private/ftp.accounts) in which each non-comment/non-blank line is a
space-separated line of (USERNAME, PASSWORD, ROOTCAP), like so:: space-separated line of (USERNAME, PASSWORD, ROOTCAP), like so::
% cat BASEDIR/private/ftp.accounts % cat BASEDIR/private/ftp.accounts
# This is a password line, (username, password, rootcap) # This is a password line, (username, password, cap)
alice password URI:DIR2:ioej8xmzrwilg772gzj4fhdg7a:wtiizszzz2rgmczv4wl6bqvbv33ag4kvbr6prz3u6w3geixa6m6a alice password URI:DIR2:ioej8xmzrwilg772gzj4fhdg7a:wtiizszzz2rgmczv4wl6bqvbv33ag4kvbr6prz3u6w3geixa6m6a
bob sekrit URI:DIR2:6bdmeitystckbl9yqlw7g56f4e:serp5ioqxnh34mlbmzwvkp3odehsyrr7eytt5f64we3k9hhcrcja bob sekrit URI:DIR2:6bdmeitystckbl9yqlw7g56f4e:serp5ioqxnh34mlbmzwvkp3odehsyrr7eytt5f64we3k9hhcrcja