Bug 8025 - Unicode usernames from different browsers are not treated equally
Summary: Unicode usernames from different browsers are not treated equally
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Web Access (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Bugzilla mail exporter
Depends on:
Reported: 2022-11-15 11:07 CET by Linn
Modified: 2022-11-15 16:47 CET (History)
0 users

See Also:
Acceptance Criteria:


Description Linn cendio 2022-11-15 11:07:07 CET
Server was a Fedora 35, and tested on webaccess with a username that did _not_ exist on the server.

When using Firefox v. 105, trying to log in with username 'test🐇er' results in the following line being logged:
> Cannot find user ''test🐇er''
On Chromium v. 103 and Safari v. 16, this is instead logged:
> Cannot find user ''test🐇er''
4.14.0 has the same behaviour, so it is not a regression. However, the name from Chromium and Safari should be fully parsed when logging this, so something is quite off here.
Comment 1 Linn cendio 2022-11-15 12:59:52 CET
Here is another scenario when dealing with a slightly more common non-ascii name.

Username: testöer

Log when using Firefox:
> Cannot find user ''testöer''
Log when using Chromium:
> Cannot find user ''test�er''
Comment 2 Linn cendio 2022-11-15 14:13:39 CET
Note that for the password, all three browsers have the same correct behaviour. Tested including åäö and different emojis in the password, and all log messages showed the characters correctly converted.

Note You need to log in before you can comment on or make changes to this bug.