'tahoe mount' command #1357
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#1357
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
(/tahoe-lafs/trac-2024-07-25/issues/6415)#comment:1 suggested a
tahoe mount
command, which would mount a Tahoe directory at a local mount point.(As for all other CLI commands, TAHOE_PATH could be given relative to the default
tahoe:
alias, an explicit alias, or an explicit URI.)I propose implementing this using SFTP+sshfs. The SFTP frontend would be changed to allow logging in with an arbitrary cap URI as root directory (#1356). Then the above mount command would be implemented by invoking
sshfs
with the-o password_stdin
option, and passing the URI on stdin. This avoids exposing the URI via the command line. Because any aliases inTAHOE_PATH
are resolved bytahoe mount
, it also avoids ambient authority weaknesses, even when an attacker is not prevented from connecting to the SFTP server.The host and port of the SFTP server would be obtained by determining the node directory as usual, and looking for a
tahoe.cfg
with ansftpdport
setting in that directory. (It might be useful to allow specifying this in a separatesftp.url
file analogous tonode.url
, I'm not sure.)Replying to davidsarah:
Note that this doesn't preclude supporting other ways to mount a Tahoe filesystem using the same
tahoe mount
syntax, if we implement other FUSE interfaces in future. There could be atahoe.cfg
setting to specify the command that is executed. For example:Out of time for 1.9.
Milestone renamed
renaming milestone
Moving open issues out of closed milestones.
Ticket retargeted after milestone closed