![]() ![]() ![]() The setup guide for servers isn't "run murmur.exe", it's "run openssl commands to generate a private key and generate a CSR" and the setup guide for clients is "if you lose your client certificates, you potentially lose all ability to connect, and permissions/rights, hope there's another admin".Īlso, the access tokens option seems absurd from a UX perspective. The onboarding is typical of non-hipster F/OSS. ![]() That's my thought too, Mumble's text chat is terribad, the UI looks like crap. The last time I used it, setup also suggested that instead of a self-signed cert, you got an email-verified mail signing certificate from an actual CA.įor comparison, Ventrilo and Teamspeak are heavily DRM encumbered, your servers go offline randomly when the licencing servers go down due to frequent attacks as they phone home and get no response, have utterly insane ToS that near totally shuts down community servers, forbid you from self hosting on your own infrastructure and tell you to buy from their 'hosting partners paying per slot', but you just get an admin password at first start of the daemon. The mumble wiki literally has the sentence "For more information about certificates, see the Wikipedia entries on Public key Certificates." PKI is barely well understood by many engineers. Setting up a client as a user and being told to set up client certificates for mTLS and export your certificates with a strong passphrase to not lose access to your server is an insanely high bar for casual gamers, though a lot more secure. This reads like the Show HN: Dropbox thread UI/UX for Mumble is typical of engineer-design. Setting up a Mumble client as a user is not complicated, ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |