BR
- Beerbelott
- beerbelott
- Europe/Stockholm
- Yes
- No
MC-52679![[Mojang] Searge (Michael Stoyke)](../../../data/assets/gravatar/searge.png){kind=small}
Upgrading my server from v1.7.5 to v1.7.7, whitelist activated, I could not connect to my server with the error message telling me I was not whitelisted, while my nickname was in the ops.txt file.
Playing around with it, I noticed that the UUID gener
fation is based on nicknames (-un-salted hash?) and that they were case-sensitiveThe problem is that v1.7.5 forced lowercase nicknames in ops.txt and white-list.txt, effectively overwriting them in that way.
The only way I could generate correct UUIDs was to edit ops.txt and white-list.txt files prior to the upgrade to v1.7.7 in order to restore the correct case of all involved nicknames.
Then, and only then, upgrade to v1.7.7 creates correct UUID and operators/whitelisted members can happily join.
Upgrading my server from v1.7.5 to v1.7.7, whitelist activated, I could not connect to my server with the error message telling me I was not whitelisted, while my nickname was in the ops.txt file.
Playing around with it, I noticed that the UUID generation is based on nicknames (-un-salted hash?) and that they were case-sensitive
The problem is that v1.7.5 forced lowercase nicknames in ops.txt and white-list.txt, effectively overwriting them in that way.
The only way I could generate correct UUIDs was to edit ops.txt and white-list.txt files prior to the upgrade to v1.7.7 in order to restore the correct case of all involved nicknames.
Then, and only then, upgrade to v1.7.7 creates correct UUIDs and operators/whitelisted members can happily join.
I understand you do not support this and your reasons.
Too bad you made the decision of storing lowercase-only nicknames in 1.7.5, having decided to create case-sensitive UUID generation in 1.7.7, making the upgrade process not seamless... One could still feel some shifts in design hiding behind the 'do not care' stand. ;o)
I experienced the same bug.
I attached the cras hreport and the part of the log file indicating the last event, maybe related (or not) to the crash.
THe fall from the high place was made by jumping into a block of water from a high place, which normally slows you down and avoids getting killed... I do no know if I died resulting from a bug or if my fall triggered it, but that death was unexpected/not normal, as tested multiple times.