Remove the # from before the “keyfile=” line, then add the following after the = symbol: Using the arrow keys, move the cursor down to the section of the file. We need to edit a file now, so start by opening your lokinet.ini file with this command: Linux servers don’t have a graphical interface, but they do ship with some in-terminal text editors. We need to set up Lokinet to always generate a keyfile in the same directory, so it will work consistently. On to Step 5: Step 5: Setting up a persistent keyfile Next, update your repository package lists again with:Ĭongrats, Lokinet is now installed and running in the background. Then run the following command to tell apt where to find the Lokinet packages:Įcho "deb $(lsb_release -sc) main" | sudo tee /etc/apt// Run the following command to install the public key used by the Lokinet dev team to sign Lokinet binaries: To install Lokinet, we need to add the Lokinet repository. Success? Congrats, you’re ready to move on to the next step: Step 3: Install Lokinet ![]() Then run which curl again to make sure curl is installed. It should output the location of your installed curl command. We’ll also need to make sure the curl command is installed before we proceed. Once this command completes, run the following command to upgrade any outdated packages currently installed on the VPS: You’ll see a bunch of package lists being downloaded. First, we’ll update our package lists to make sure our VPS sees the most recent versions of all available packages. Once you’ve logged in, we’re ready to roll. As you learn more about Linux, you’ll get more familiar with these best practices. More advanced users can and should disable root password access and instead use SSH keys, but if that sounds hard, don’t worry about it for now. It’ll prompt you for a password which will usually be provided to you by the VPS host. Start by opening a command prompt on your local machine (Terminal on macOS, any command prompt on Linux, or PowerShell on Windows 10). Once you have access to your new VPS, you’re almost ready to install Lokinet, but there’s a little bit of preparatory work to do first. ![]() Try, or if you want to pay in Loki/Oxen! When ordering, select Ubuntu 20.04 or Debian 10. Mumble’s chat server has extremely low system requirements, so a VPS with any amount of storage and at least 512MB RAM will do the trick - you can find VPSs that meet these requirements for around US$3 a month. ![]() You could run the Mumble server from your own computer instead, but if you want the server to stay up 24/7, without having to leave your own PC on all the time, a VPS is the way to go. The first thing you’ll want to do is rent yourself a VPS (Virtual Private Server) to host your Mumble voice chat server. We’ll walk you through every step! With that, let’s get to it. If this is your first time using SSH and Linux stuff, don’t stress. So long as you trust the device that you run the Mumble server on (which you can, because it’s yours), you can be certain that no one else on earth can eavesdrop on your conversation - or even know that you’re connected to the server at all. Well what if you could run a Mumble server over Lokinet, combining Mumble’s ease of use with Lokinet’s security and anonymity to create the ultimate secure voice chat service? In this article, we’re going to cover how to do exactly that - with just 15 minutes of your time and $3 a month, you and your organisation can create one of the most secure voice chat platforms possible.Ī Mumble server running over Lokinet on a server you control gives you absolute certainty that your voice conversations, associated metadata, and other Mumble activity cannot be stored or recorded, because no computer ever knows who is talking to whom - not even the Mumble server itself. Even though Mumble can support a large number of users, you may find it helpful to limit the number of simulatenous users, especially if your server is not password-protected.Mumble is a fantastic open-source voice chat platform known for its reliability and ease of use.Īnd Lokinet is a cutting-edge onion routing network that offers unparalleled security and anonymity potential. To modify the maximum number of simultaneous users on your Mumble server look for the line “users=100” and modify the value according to your use-case. To personalize the welcome message for your Mumble server, look for the line starting with “welcometext= ” and enter your message. To require users to enter a pasword to join your Mumble server, find the line “serverpassword= ” and add the desired password. The following are some configuration options you may find useful: Do not remove this sign unless you want to activate the variable. Remove the “#” for variables you want to activate. All configuration variables are commented out with lines starting with a #.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |