[tahoe-dev] [tahoe-lafs] #1353: make the FUSE interface be a supported, first-class feature

[tahoe-lafs]

#1353: make the FUSE interface be a supported, first-class feature
-------------------------------+--------------------------------------------
     Reporter:  zooko          |       Owner:  somebody 
         Type:  enhancement    |      Status:  new      
     Priority:  major          |   Milestone:  undecided
    Component:  documentation  |     Version:  1.8.2    
   Resolution:                 |    Keywords:  fuse docs
Launchpad Bug:                 |  
-------------------------------+--------------------------------------------

Comment (by gdt):

 The SFTP interface is cool, and I think should stay, but saying our fuse
 answer is to use it seems kludgy, and extended attributes and caching will
 be harder.

 We need a way for someone to use the CLI to do
 {{{
 tahoe mount [ALIAS:][PATH] [system-path]
 }}}
 or perhaps just alias:, and require an alias for a sub-path.  Note that
 there is no sftp login, no ssh credentials, just reading the cap out of
 the .tahoe directory.   Perhaps system-path defaults to ~/TAHOE/ALIAS.
 the FUSE module should then allow requests only from the same uid that did
 the mount, and maybe root, and have an option to allow anyone who could
 access the original directory to do things - I'm not sure but one has to
 translate system access control to tahoe access control.  Perhaps this is
 a whole separate program, but it seems core, and I think if it worked well
 many people would be using it.

 This will then point out that having files be chmod +x would be sensible,
 which leads to tahoe storing attributes.

 The really hard part is dealing with immutable files and the illusion of
 writing to them.  Maybe they're just read-only and one has to write/rename
 which is what should happen anyway.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1353#comment:1>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage