In a gaming scenario (which is what my server is used for) you typically have many users with multiple computers. These computers are probably set up with the same username; possibly (if the server is secured) registered with the same certificate.
Inevitably, a user will have a friend over, or something, and want to use his desktop and laptop at the same time (or desktop & desktop, etc). This is a hassle with Mumble, because two physical users then want to log in with the same credentials. Expecting them to change logins, or worse, bring their certificates on a USB key, for a LAN party, is an unreasonable demand.
I propose a new configuration line in the Murmur conf file - "logins_per_user" which would control how many multiple logins the server will accept concurrently for the same credentials. Defaulting to zero, this would let administrators selectively relax security as desired, and remove the need for "User_Laptop" logins, which are ugly.
On the backend, the server could simply append numbers to the username ("user", "user", "user", etc), possibly with some flag that indicates they are a guest user. To prevent naming collisions (eg - what if an actual user is already called "user "?), perhaps an additional configuration could specify which characters to use when indicating the guest numbers. An administrator could specify "[ ]" as the guest brackets, then disallow usernames with brackets in them via the username regex.
If handled correctly, my hope is that this would be possible to implement without a client change - murmur would essentially do this translation on the backend, and simply present the mumble client with new usernames.
Log in to post a comment.