Ticket #229 (accepted enhancement)

Opened 8 years ago

Last modified 8 years ago

Allow blank username

Reported by: anonymous Owned by: alamaison
Priority: critical (affects core workflow) Milestone: 1.0 Version 1
Component: authentication Version: 0.7.3
Keywords: Cc:


Our SFTP server is configured to ONLY use a public key. The username and password are blank/not used.

I am unable to connect because Swish insists on entries in these fields.

Change History

comment:1 Changed 8 years ago by alamaison

  • Status changed from new to accepted
  • Summary changed from Cannot connect using only a public key to Allow blank username
  • Priority changed from major (affects peripheral workflow) to critical (affects core workflow)
  • Version set to 0.7.3
  • Milestone set to 1.0 Version 1
  • Type changed from defect to enhancement

Interesting suggestion. We didn't even think the SSH spec allowed a blank username but we've checked and can't find anything forbidding it.

The problem now is how to distinguish a blank username from the user not specifying one and wanting to be asked every time. The latter is not a feature yet but we planned to change Swish so that not giving a username meant the user would be prompted for one.

Note: See TracTickets for help on using tickets.