-
Confirmed with the 2 latest client snapshots and the 9a7e70 server snapshot. Renaming a user to a name that already exist doesn't seem to scare the server anymore. He simply doesn't do it.
Can be closed :)
2009-10-30 13:36:54 UTC in Mumble
-
Updated the server a few days ago and found a similar case of 2 users with a small difference (1 named right, 1 named wrong). Tried to rename the wrong one and it seems that it has no effects anymore.
The log shows that renaming the user was attempted:
2009-10-30 15:03:27.618 1 => Renamed user 73 to 'IM TNTY gillopi'
But the process didn't fault away this time. I'm on...
2009-10-30 13:30:42 UTC in Mumble
-
Not at the moment it happened. I was warned by email by a user that it went down. I restarted it, reproduce what he did 2 times to confirm. Both times having the same effect when renaming the user. the daemon/process would simply stop.
I then deleted the 2 users with the similar names (but different start) directly in the DB (phpMyAdmin).
2009-10-30 02:57:24 UTC in Mumble
-
While I understand your concerns, I would say that it is to the admin to decide based on the power you gave him. Eavesdropping via linked channel (or not) is bound by the fact that it is possible via the ACL and because the admin allowed it. For example, only people in my "directors" group can link channels. So unless a director, nobody else can link channels.
In fact, all you are mentioning is...
2009-10-29 21:10:39 UTC in Mumble
-
Was in my log: 2009-10-27 20:19:13.234 SQL Error [UPDATE `mumbleopen_users` SET `name`=? WHERE `server_id` = ? AND `user_id`=?]: Duplicate entry '1-INIT DICIO Charlie Murdock' for key 2 QMYSQL3: Unable to execute statement
When I checked the DB after the crash to rename the user, I noticed there was 2 of them with similar name:
DICIO Charlie Murdock
INIT DICIO Charlie Murdock
Seems...
2009-10-27 23:14:18 UTC in Mumble
-
The server version is 8af721 so it's a bit late but I'll change it tomorrow to the latest. I won't rename a user again tonight or I'll get shot in the face. :)
2009-10-27 19:49:08 UTC in Mumble
-
1260b9
Renaming a user in the "Registered Users" window kills the server.
2009-10-27 19:42:06 UTC in Mumble
-
aw right, you can scrap the whole thing and dump it in the hall of shame.
The problem was related to my script my users were using in the game that gives them the ability to change their password. The script was somehow changing both their users and the SuperUser pass. A missed field change in the script between 1.1.8 and 1.2.0 is responsible for all this.
Sorry for that one - you can...
2009-10-23 09:18:51 UTC in Mumble
-
Woke up this morning and looked directly into the database to see if the password was changed and it was. Totally different. Searched the database and found another user having the same as if somehow, the SuperUser password was taking the password of someone else during the night.
I'm digging to see if that user did something in particular in the last few hours.
2009-10-23 08:34:34 UTC in Mumble
-
In the MySQL database. In fact, looking at the string of the password now, I think it's not the same as before I changed it back to what it was supposed to be.
Hard to explain I admit, basically, I end up with my SuperUser unable to log in because of password. Setting it back in the DB fixes it.
Another note - using Mumble both at home and at work.
2009-10-22 22:01:11 UTC in Mumble
