diff options
Diffstat (limited to 'content')
| -rw-r--r-- | content/git.md | 2 | ||||
| -rw-r--r-- | content/jitsi.md | 2 | ||||
| -rw-r--r-- | content/mumble.md | 134 | ||||
| -rw-r--r-- | content/radicale.md | 6 | ||||
| -rw-r--r-- | content/wireguard.md | 15 |
5 files changed, 151 insertions, 8 deletions
diff --git a/content/git.md b/content/git.md index f11d79d..7cb0121 100644 --- a/content/git.md +++ b/content/git.md @@ -100,7 +100,7 @@ chown git:git -R /var/git/.ssh # Make the created directory and contents to be o ### Syncing a new repository with your server -How that we've set that up, we can push a repository we have on our computer to +Now that we've set that up, we can push a repository we have on our computer to that newly created bare repo. First, on our local computer, we run a command like this: ```sh diff --git a/content/jitsi.md b/content/jitsi.md index 82246dd..0df893b 100644 --- a/content/jitsi.md +++ b/content/jitsi.md @@ -175,7 +175,7 @@ You now need to register some users in [Prosody](/prosody), you can do so manually using `prosodyctl`: ```sh -prosodyctl register <username> meet.example.org <password> +prosodyctl register <username> meet.example.org <password> ``` Finally, restart `prosody`, `jicofo`, and `jitsi-videobridge2`: diff --git a/content/mumble.md b/content/mumble.md new file mode 100644 index 0000000..2c475b6 --- /dev/null +++ b/content/mumble.md @@ -0,0 +1,134 @@ +--- +title: "Mumble" +icon: 'mumble.svg' +tags: ['service'] +date: 2023-07-2 +short_desc: 'Open Source, Low Latency, High Quality Voice Chat.' +--- + +[Mumble](https://mumble.info) is an open source, low latency and high quality voice chat software, being the best open source alternative to TeamSpeak. +VoIP communications are mandatory encrypted by default using OCB-AES128, it has integrations for gamers (like overlays), it's stable and it's resource friendly. + +The server can also be run [behind Tor](https://gitlab.torproject.org/legacy/trac/-/wikis/doc/TorifyHOWTO/Mumble) without any issue. + +## Installation + +Mumble has a Debian repository for client and server, however it's very outdated so we are going to build the server instead. + +**I suggest to build both binaries on your local machine and [transfer the `mumble-server` to your remote server using `spc`](#extra).** + + +Install dependencies: +```sh +apt install build-essential cmake pkg-config qtbase5-dev qtchooser qt5-qmake qtbase5-dev-tools qttools5-dev qttools5-dev-tools libqt5svg5-dev libboost-dev libssl-dev libprotobuf-dev protobuf-compiler libprotoc-dev libcap-dev libxi-dev libasound2-dev libogg-dev libsndfile1-dev libspeechd-dev libavahi-compat-libdnssd-dev libxcb-xinerama0 libzeroc-ice-dev libpoco-dev g++-multilib +``` + +Git clone the repo. + +```sh +git clone https://github.com/mumble-voip/mumble.git && cd mumble +``` + +Initialize all the submodules. + +``` +git submodule update --init +``` + +Create a build directory and run `cmake`. +Cmake will create all the necessary files to build the mumble-server and client. + +```sh +mkdir build && cd build && cmake .. +``` + +Build using `cmake`. + +```sh +cmake +``` + +After the build you will now find a file named `mumble-server`, one `mumble` (which is the client) and a file named `mumble-server.ini` (aka the config file). + +## Running your Mumble server + +If you built it on local machine you can check out [how to move it to your remote server](#extra) first. + +After that, start with making your `mumble-server` executable and move it in `/usr/bin`. + +```sh +chmod +x mumble-server && mv mumble-server /usr/bin +``` + +Create a folder in `/etc/` move your config files there. + +```sh +mkdir /etc/mumble && mv mumble-server.ini /etc/mumble +``` + +Now we can run the server passing the config and a superuser password that can be used to connect and authenticate as an administrator from any client + +```sh +mumble-server -ini mumble-server.ini -supw <your_password> +``` + +Check if it's running in the backgroud with `ps aux`. + +```sh +ps aux | grep mumble-server +``` + +You will have an output like this. + +```sh +root 127181 0.1 0.1 261064 21640 ? Sl 19:18 0:01 ./mumble-server +root 127689 0.0 0.1 112956 22572 ? Sl 19:19 0:00 ./mumble-server +``` + +## Connecting to your mumble-server as a SuperUser + +You will probably will be left with your `mumble` binary in the build folder on your local machine. + +Now you should make it executable and move it in the `/usr/bin` folder. + +```sh +chmod +x mumble && mv mumble /usr/bin +``` + +Run it the GUI with one command. + +```sh +mumble +``` + +You will have something like this opening up. + +{{< img src="/pix/mumble/mumble-1.png" alt="connect window" >}} + +Click on the button `Add New...` and fill out the information need to connect to your server. + +{{< img src="/pix/mumble/mumble-2.png" alt="add server window" >}} + +If you haven't edited the port, `64738` will be default one. + +Click on `Ok`, select your server from the list and click `Connect`. + +**Now you are connected to your very own Mumble server as a SuperUser!** + +--- + +## Extra + +### Move binary with scp + +Move your binary to the folder `~` of your remote server. + +```sh +spc <your_binary> root@<your_server_ip>:~ +``` + +--- + +Written by [NotMtth](https://notmtth.xyz) (Tor access warning) + +Donate Monero at: `donate.notmtth.xyz` ([OpenAlias](https://openalias.org/))
\ No newline at end of file diff --git a/content/radicale.md b/content/radicale.md index b24f8ef..c37f22c 100644 --- a/content/radicale.md +++ b/content/radicale.md @@ -49,6 +49,12 @@ Execute the following command to add a new user to Radicale. htpasswd -B -c /etc/radicale/users username ``` +To create additional users, htpasswd is used again but without the additional modifier. + +```sh +htpasswd -B /etc/radicale/users username2 +``` + As Radicale stands now it is fully functional and after starting it by executing its binary, can be accessed under example.org:5232. But there are two additional things we can do to make using and managing Radicale diff --git a/content/wireguard.md b/content/wireguard.md index 93e722f..3e7d571 100644 --- a/content/wireguard.md +++ b/content/wireguard.md @@ -1,8 +1,9 @@ --- -title: "Wireguard" -date: 2022-07-26 -icon: 'wireguard.svg' -tags: ['service'] +title: Wireguard +date: 2022-07-26T00:00:00.000Z +icon: wireguard.svg +tags: + - service short_desc: "Fast, Modern, Secure VPN Tunnel" --- @@ -16,6 +17,7 @@ As an example, we'll be using a virtual 172.16.0.0/24 network, but any private i ## Installation ### On the Server + Install the WireGuard management tools: apt install wireguard @@ -29,6 +31,7 @@ Run the following command to apply the change: sysctl -w net.ipv4.ip_forward=1 ### On the Client + Use your package manager to install the WireGuard Management Tools. On Arch and Fedora based distros the package is `wireguard-tools`. For Debian based, it's listed above. @@ -37,7 +40,6 @@ Create the public and private keys for your machine: sudo bash -c "umask 077 ; wg genkey > /etc/wireguard/client_priv.key" sudo bash -c "wg pubkey < /etc/wireguard/client_priv.key > /etc/wireguard/client_pub.key" - ### Back to the Server Generate the public and private keys for your server: @@ -106,6 +108,7 @@ there's a good chance you're behind a corporate firewall. Read on. ## WebSocket Tunnel #### Note on TLS + If your server hosts a website with https, you won't be able to use port 443 to obfuscate your WireGuard packets as TLS traffic. You may use some other innocuous port, but there's no guarantee you'll punch through the picky firewall. @@ -145,7 +148,7 @@ Download and install wstunnel and a helper script: wget https://github.com/erebe/wstunnel/releases/download/v4.0/wstunnel-x64-linux sudo mv wstunnel-x64-linux /usr/local/bin/wstunnel sudo chmod +x /usr/local/bin/wstunnel - wget https://codeberg.org/onasaft/sbx/raw/branch/main/vpn/wstunnel.sh + wget https://raw.githubusercontent.com/jnsgruk/wireguard-over-wss/master/wstunnel.sh sudo mv wstunnel.sh /etc/wireguard/wstunnel.sh sudo chmod +x /etc/wireguard/wstunnel.sh |