Bug #4461
OTR problems caused by mixed case usernames
| Status: | Closed | Start date: | 01/27/2015 | |
|---|---|---|---|---|
| Priority: | Urgent | Due date: | ||
| Assignee: | n8fr8 | % Done: | 0% | |
| Category: | - | |||
| Target version: | v14.2 bug fix update! | |||
| Component: |
Description
From irc:
<n8fr8> we had a bunch of people setup chatsecure, and it worked really well for all of them, except one guy
<n8fr8> and i realized, he had entered an uppercase username when he created his account "Foobar@dukgo.com"
<n8fr8> now, when we registerd on the server, and send messages it is standardized to lowercase "foobar@dukgo.com/ChatSecure-1234" etc
<n8fr8> but in the local account db it is still "Foobar@dukgo.com"
<n8fr8> and the local key that is generated is assigned to "Foobar@dukgo.com"
<n8fr8> so when the OTR sesison init happens, it can't find a key
<n8fr8> i confirmed this by creating a new account on the same problematic device with a lowercase name, and OTR worked
History
#1 Updated by hans almost 3 years ago
is there any reason to store the case of the username? Sounds like the account input field should have a validator that automatically downcases the letters as the user types them. Then the username will be lowercase everywhere. There would need to be a converter for old stored account info.
#2 Updated by n8fr8 almost 3 years ago
hans wrote:
is there any reason to store the case of the username? Sounds like the account input field should have a validator that automatically downcases the letters as the user types them. Then the username will be lowercase everywhere. There would need to be a converter for old stored account info.
That is exactly what I implemented in the fix (the normalizing on account setup, as well as remove spaces, other non-valid characters).
I did not yet implement a converter for old accounts.
#3 Updated by n8fr8 over 2 years ago
- Target version set to v14.2 bug fix update!
#4 Updated by n8fr8 over 2 years ago
- Status changed from New to Resolved
#5 Updated by n8fr8 over 2 years ago
- Status changed from Resolved to Closed