accept trailing slashes on directory cap URIs #2036
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
1 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#2036
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Does some standard say this is required? dircap URIs are not POSIX directories, so this notion seems odd at first read.
No standard applies here. However, the CLI accepts the syntax "URI:.../path", so by analogy with POSIX paths, it should also accept a trailing slash in contexts where a directory is accepted.
(23:08:24) zooko: Well, what happens when you use the "sftp" client to connect to localhost port 8022?
(23:09:14) rhaeder: it says connected
(23:09:31) rhaeder: remote readdir("/"): Permission denied
(23:09:41) rhaeder: a simple "ls"
(23:10:09) zooko: Okay, the Tahoe-LAFS process that runs that SFTP server -- does it also listen on a web port?
(23:10:19) rhaeder: yes
(23:10:41) zooko: Does the welcome page that it shows on that web port say that it is connected to an introducer and at least one storage server?
(23:10:51) rhaeder: the same URI gives me my storage directory
(23:10:58) zooko: I wonder what "permission denied" means there...
(23:11:27) zooko: Yeah, double-check whether the cap in the SFTP passwords file is the same as the cap you're using in the WUI.
[...]
(23:13:02) zooko: So the cap that it uses when you do "ls" is something it looks up from its accounts file.
(23:13:28) zooko: The username and password that you use to login to the SFTP Server, it looks up that username in the accounts file and gets the cap from there. Then it uses that cap.
(23:13:53) zooko: It sounds like you want that to be the same cap that you are using when you browse your storage directory using the WUI.
(23:13:59) zooko: Is that cap written into the SFTP accounts file?
(23:14:24) rhaeder: ah, my private/accounts file contained a trailing slash at the cap URI
(23:14:28) zooko: Aha!
(23:14:31) zooko: So that was a bad error message.
(23:14:48) rhaeder: working! :)
(23:14:48) zooko: It said "Permission denied". Useless! It should have said something like "This isn't a well-formed cap."
(23:14:50) zooko: Right?
(23:14:53) zooko: Yay!
(23:15:07) rhaeder: yes, that message would be much better understandable :)
(23:15:18) zooko: Please send email to tahoe-dev@tahoe-lafs.org saying that you got it working, because Greg Troxel isn't on IRC, and he disbelieves that people use Tahoe-LAFS with FUSE. ;-)
(23:15:31) rhaeder: ;)
(23:15:34) zooko: I'll open an issue ticket about that error message if there isn't already one...