FTP/SFTP: report malformed cap at login instead of use-time #1965

Open
opened 2013-05-06 15:15:37 +00:00 by zooko · 3 comments
zooko commented 2013-05-06 15:15:37 +00:00
Owner

I was experimenting with the SFTP server and I accidentally pasted a malformed (truncated) cap into the config. It reports this reasonably well when I try to use it:

lftp acct@127.0.0.1:~> ls
ls: Access failed: cannot list an unknown cap as a directory. Upgrading the gateway to a later Tahoe-LAFS version may help

(Actually that's not a great error message — it should tell me that this is a malformed cap, not a cap of an unknown type — but that's the topic of a different ticket.)

It would be better if it reported this error as soon as I login rather than waiting until I try to "ls" something.

I was experimenting with the SFTP server and I accidentally pasted a malformed (truncated) cap into the config. It reports this reasonably well when I try to use it: ``` lftp acct@127.0.0.1:~> ls ls: Access failed: cannot list an unknown cap as a directory. Upgrading the gateway to a later Tahoe-LAFS version may help ``` (Actually that's not a great error message — it should tell me that this is a malformed cap, not a cap of an unknown type — but that's the topic of a different ticket.) It would be better if it reported this error as soon as I login rather than waiting until I try to "ls" something.
tahoe-lafs added the
code-frontend
normal
enhancement
1.10.0
labels 2013-05-06 15:15:37 +00:00
tahoe-lafs added this to the undecided milestone 2013-05-06 15:15:37 +00:00
daira commented 2013-05-06 20:11:21 +00:00
Author
Owner

The issue of reporting invalid cap URIs as if they were unknown, is #1112. (That ticket currently describes the issue only for the CLI, but it's the same underlying problem.)

The issue of reporting invalid cap URIs as if they were unknown, is #1112. (That ticket currently describes the issue only for the CLI, but it's the same underlying problem.)
tahoe-lafs changed title from FTP/SFTP/FUSE: report malformed cap at login instead of use-time to FTP/SFTP: report malformed cap at login instead of use-time 2013-05-06 20:11:21 +00:00
daira commented 2013-05-06 20:15:24 +00:00
Author
Owner

The gateway could report the invalid URI at start-up time as well as at login.

The gateway could report the invalid URI at start-up time as well as at login.
zooko commented 2013-05-06 21:04:42 +00:00
Author
Owner

Replying to daira:

The gateway could report the invalid URI at start-up time as well as at login.

Good idea, thanks! And thanks for the link to #1112.

Replying to [daira](/tahoe-lafs/trac-2024-07-25/issues/1965#issuecomment-133141): > The gateway could report the invalid URI at start-up time as well as at login. Good idea, thanks! And thanks for the link to #1112.
tahoe-lafs added
code-frontend-ftp-sftp
and removed
code-frontend
labels 2014-12-02 19:49:57 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#1965
No description provided.