Changes between Version 1 and Version 2 of Ticket #1356


Ignore:
Timestamp:
2011-02-04T22:34:22Z (14 years ago)
Author:
davidsarah
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1356

    • Property Keywords test-needed design-review-needed added
    • Property Summary changed from SFTP: allow logging in with an arbitrary cap URI as root directory to SFTP and FTP: allow logging in with an arbitrary cap URI as root directory

  • Ticket #1356 – Description

    v1 v2  
    1 The SFTP frontend should allow logging in with username {{{uri}}}, and password an arbitrary cap URI.
     1The SFTP and FTP frontends should allow logging in with username {{{uri}}}, and password an arbitrary cap URI.
    22
    3 This can then be used to implement a {{{tahoe mount}}} command (#1357), as suggested in ticket:1353#comment:3.
     3Implementing this for SFTP can then be used to support a {{{tahoe mount}}} command (#1357), as suggested in ticket:1353#comment:3. For both SFTP and FTP, it is potentially useful to be able to log in with a root URI without having set up an account for it in the {{{ftp.accounts}}} file. (SFTP and FTP use the same code in [source:src/allmydata/frontends/auth.py] to handle logins, so it is simpler for them to behave the same.)
    44
    55Note that you can already access an arbitrary cap URI via the {{{/uri/}}} directory, but that does not have nearly as nice usability properties, because you can't access aliases that way. (Allowing access to aliases would provide ambient authority and so is not capability-secure.)