New issue
Advanced search Search tips

Issue 883219 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 12
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

nassh: whitespaces allowed and not detected in the username (maybe other fields too)

Project Member Reported by vvvv@google.com, Sep 12

Issue description

Chrome Version       :  68.0.3440.118
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari:
    Firefox:
       Edge:

What steps will reproduce the problem?
(1) open ssh extension (chromeos)
(2) enter your username and add a whitespace
(3) press connect
What is the expected result?

whitespace stripped OR highlighted

What happens instead?

access denied error. This is even more common if the username is copied

Please provide any additional information below. Attach a screenshot if
possible.

 
Status: WontFix (was: Unconfirmed)
Summary: nassh: whitespaces allowed and not detected in the username (maybe other fields too) (was: whitespaces allowed and not detected in the username (maybe other fields too))
whitespace is valid in usernames, even a username made up purely of whitespace.  it's probably not a common thing, but i'm not going to ban it to catch bad copy & paste.

i could add a highlight to it, but i'm honestly not seeing it being worth the effort in terms of trade-off: i expect the incident rate of accidentally using whitespace is quite low.

Sign in to add a comment