Opened at 2013-05-06T15:15:37Z

Last modified at 2014-12-02T19:49:57Z

#1965 new enhancement

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

Reported by: zooko Owned by:
Priority: normal Milestone: undecided
Component: code-frontend-ftp-sftp Version: 1.10.0
Keywords: ftpd sftp usability error Cc:
Launchpad Bug:

Description

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.

Change History (4)

comment:1 Changed at 2013-05-06T20:11:21Z by daira

  • Keywords ftpd added; ftp fuse removed
  • Summary changed 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

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.)

comment:2 follow-up: Changed at 2013-05-06T20:15:24Z by daira

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

comment:3 in reply to: ↑ 2 Changed at 2013-05-06T21:04:42Z by zooko

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.

comment:4 Changed at 2014-12-02T19:49:57Z by warner

  • Component changed from code-frontend to code-frontend-ftp-sftp
Note: See TracTickets for help on using tickets.