-
Notifications
You must be signed in to change notification settings - Fork 13
Open
Description
I'm submitting a ...
- bug report
What is the current behavior? [REQUIRED]
- If username in DB is lower-case but user used upper case to log-in, the server rejects his first packet due to ticket mismatch.
Steps to reproduce [REQUIRED]
- Create user with lower-case (eg. helloworld)
- Login with upper-case (eg. Helloworld)
What is the expected behavior? [REQUIRED]
User should be able to check-in since his packet was valid.
Other informations [OPTIONAL]
We could fix this by lower-casing both usernames in the check here:
| userInfoPacket.Username != packet.Sender.User.Username) |
Log
[Error] - Rejecting packet from 0.0.0.0:51539 (user: helloworld vs Helloworld, ti
cket 3311448694 vs 3311448694) for invalid user-ticket combination.
[Info] - Killing off client.