summaryrefslogtreecommitdiff
path: root/content
diff options
context:
space:
mode:
Diffstat (limited to 'content')
-rw-r--r--content/git.md2
-rw-r--r--content/jitsi.md2
-rw-r--r--content/radicale.md6
-rw-r--r--content/wireguard.md15
4 files changed, 17 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 &ltusername> meet.example.org &ltpassword>
+prosodyctl register <username> meet.example.org <password>
```
Finally, restart `prosody`, `jicofo`, and `jitsi-videobridge2`:
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