![]() ![]() Selecting previously unselected package mumble. Unpacking libavahi-compat-libdnssd1:amd64 (0.7-4ubuntu7) … Preparing to unpack …/libavahi-compat-libdnssd1_0.7-4ubuntu7_b … ![]() (Reading database … 386152 files and directories currently installed.) Selecting previously unselected package libavahi-compat-libdnssd1:amd64. The following NEW packages will be installed:Ġ to upgrade, 2 to newly install, 0 to remove and 18 not to upgrade.Īfter this operation, 8,513 kB of additional disk space will be used. The following additional packages will be installed: Press “Add” from the action bar to add a server first + Ubuntu Install sudo apt install mumble -y uilding dependency tree Generating a certificate is highly recommended, and necessary for connection to some servers. WRT to distributing registry files, you could simply replicate that functionality with an "Import / Export Configuration" menu item or wizard in the same manner as the "Import / Export Certificate" wizard.Mumble Client Essentials. I would prefer to use plaintext storage instead. It is simply an abstraction layer that interacts with the certificate stores available on the users system, including Windows Crypto, Apple Ke圜hain, Gnome KeyRing, and KDE RE: SQLite That being said, I did find a Qt5 library for managing passwords known as Qt Keychain that likely also supports, or could support, certificate storage. That sort of thing, is needless to say, not very helpful in the long run. Requiring a certificate store for Linux would mean requiring a specific store for Linux, and it is all too often that these things are so heavily integrated with their desktop enviroment that you could easily see KDE base, for instance, become a hard dependency of the mumble client. The downside to using the keychain on OSX, if I recall, would be needing to prompt the user for their password every time the cert is needed.Īdditionally, there is no user-specific cert store for Linux that will reliably be found across different configurations. Realistically, I should be able to extract a mumble client profile on one platform and have it work on any other supported platform simply by placing it in the configuration If we stored the cert in the cert store it would still be easier to extract ICE due to the availability of forensics/data recovery software to analyze the cert store / keychain. Attempt to get mumble to run in WINE or use a VM.Export a registry snapshot of Software\Mumble.I got as far as extracting the REG_BINARY cert value, and gave up, because converting that to a nf-friendly value is simply no small task. I was trying to help someone recover their key from windows. There appears to be no reason to keep this data in such manners, and it has only caused me frustration. That it uses the nf approach for all platforms. I propose that mumble either move settings and certificate storage in to an SQLite database, or On Linux, the configuration is stored in some manner of INI file, nf.On OSX, the configuration is stored in a plist file, and I'm not sure what that looks like.On Windows, the mumble configuration lives entirely in binary storage hell - NTUSER.DAT (HKCU).Currently, mumble stores client data, including certificates, as follows: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |