[tahoe-dev] Use Tahoe as a real-time distributed file system?

Greg Troxel gdt at ir.bbn.com
Wed May 25 15:48:30 PDT 2011


"Zooko O'Whielacronx" <zooko at zooko.com> writes:

> This is great feedback! Could you please open tickets on
> http://tahoe-lafs.org for any of these issues which aren't already
> ticketed?
>
> Please add the "sftp" and "fuse" keywords to the tickets, and also
> link them to #1353, which is a meta-ticket tracking those other
> tickets.

Done, but my trac-ticket-fu is nto that great, so please feel free to
fix anything I did.


1. sftp not taking pubkey auth

From
  http://tahoe-lafs.org/~zooko/repos/tahoe/docs/frontends/FTP-and-SFTP.txt

I see

    To use the first form, create a file (probably in
    BASEDIR/private/ftp.accounts) in which each non-comment/non-blank line
    is a
    space-separated line of (USERNAME, PASSWORD/PUBKEY, ROOTCAP), like so:

     % cat BASEDIR/private/ftp.accounts
     # This is a password line, (username, password, rootcap)
     alice password
     URI:DIR2:ioej8xmzrwilg772gzj4fhdg7a:wtiizszzz2rgmczv4wl6bqvbv33ag4kvbr6prz3u6w3geixa6m6a
     bob sekrit
     URI:DIR2:6bdmeitystckbl9yqlw7g56f4e:serp5ioqxnh34mlbmzwvkp3odehsyrr7eytt5f64we3k9hhcrcja

     # and this is a public key line (username, pubkey, rootcap)
     carol ssh-rsa
     AAAAB3NzaC1yc2EAAAABIwAAAQEAv2xHRVBoXnwxHLzthRD1wOWtyZ08b8n9cMZfJ58CBdBwAYP2NVNXc0XjRvswm5hnnAO+jyWPVNpXJjm9XllzYhODSNtSN+TXuJlUjhzA/T+ZwdgsgSAeHuuMQBoWt4Qc9HV6rHCdAeMhcnyqm6Q0sRAsfA/wfwiIgbvE7+cWpFa2anB6WeAnvK8+dMN0nvnkPE7GNyf/WFR1Ffuh9ifKdRB6yDNp17bQAqA3OWSFjch6fGPhp94y4g2jmTHlEUTyVsilgGqvGOutOVYnmOMnFijugU1Vu33G39GGzXWla6+fXwTk/oiVPiCYD7A7WFKes3nqMg8iVN6a6sxujrhnHQ==
     warner at fluxx
     URI:DIR2:6bdmeitystckbl9yqlw7g56f4e:serp5ioqxnh34mlbmzwvkp3odehsyrr7eytt5f64we3k9hhcrcja

    [TODO: the PUBKEY form is not yet supported]

Filed as

  http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1411

2. listening on public interfaces

The bits about not listening on the net is not really a problem with
the sftp implementation as (for me) a hint that using sftp to implement
vfs integration has a minus.  I think this partly comes from a
how-to-do-things different viewpoint; I view a tahoe gateway as
something that should be on every machine, and using sftp to a remote
gateway seems like an odd thing to want to do.

filed as:

  http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1410

3.  lack of feeling like native FUSE is already at:

http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1353

http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1357

http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1356
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20110525/fcde5bee/attachment.pgp>


More information about the tahoe-dev mailing list