middleware

cockpit
pihole forwardauth
2021-05-31 15:08:52 -04:00 · 2021-05-31 14:59:16 -04:00 · 2021-05-31 14:54:06 -04:00 · 2021-05-31 14:20:50 -04:00 · 2021-05-31 12:01:00 -04:00
22 changed files with 101 additions and 405 deletions
@@ -1,7 +1,7 @@
 # Mistborn
-A secure platform for easily standing up and managing your own cloud services: including firewall, ad-blocking, and multi-factor WireGuard VPN access
+A secure platform for easily standing up and managing your own cloud services: including firewall, ad-blocking, and multi-factor Wireguard VPN access
-![Mistborn WireGuard](https://gitlab.com/cyber5k/public/-/raw/master/graphics/home.mistborn_wireguard_.png)*WireGuard Management in Mistborn*
+![Mistborn Wireguard](https://gitlab.com/cyber5k/public/-/raw/master/graphics/home.mistborn_wireguard_.png)*Wireguard Management in Mistborn*
 As featured in [Linux Magazine](https://www.linux-magazine.com/Issues/2020/240/Mistborn/(language)/eng-US) (Linux Pro Magazine in North America) in November 2020
@@ -13,7 +13,7 @@ As featured in [Linux Magazine](https://www.linux-magazine.com/Issues/2020/240/M
 # What is Mistborn
 The term [Mistborn](http://www.brandonsanderson.com/the-mistborn-saga-the-original-trilogy) is inspired by a type of powerful Allomancer in Brandon Sanderson's Cosmere.
-Mistborn started as a passion project for a husband and father protecting his family. Certain family members insisted on connecting their devices to free public WiFi networks. We needed a way to secure all family devices with a solid VPN (WireGuard). Once we had that we wanted to control DNS to block ads to all devices and block malicious websites across all family devices. Then we wanted chat, file-sharing, and webchat services that we could use for ourselves without entrusting our data to some big tech company. And then... home automation. I know I'll be adding more services so I made that easy to do.
+Mistborn started as a passion project for a husband and father protecting his family. Certain family members insisted on connecting their devices to free public WiFi networks. We needed a way to secure all family devices with a solid VPN (Wireguard). Once we had that we wanted to control DNS to block ads to all devices and block malicious websites across all family devices. Then we wanted chat, file-sharing, and webchat services that we could use for ourselves without entrusting our data to some big tech company. And then... home automation. I know I'll be adding more services so I made that easy to do.
 As an [Offensive Security Certified Professional (OSCP)](https://resources.infosecinstitute.com/certification/the-oscp-certification-and-exam/), I designed Mistborn thinking about how it would be attacked by both external and internal threats. In making design trade-off decisions I tend to the paranoid. See [Technical and Security Insights](#technical-and-security-insights).
@@ -21,7 +21,7 @@ Ideal for teams who:
 - hate internet ads
 - need to be protected from malicious internet domains
 - need to collaborate securely
- need multi-factor authentication for WireGuard
+- need multi-factor authentication for Wireguard
 - want to retain sole ownership of their data
 - want to easily grant and revoke access to people and devices via a simple web interface
 - want secure internet access wherever they are
@@ -32,7 +32,7 @@ See the [Mistborn Network Security](https://gitlab.com/cyber5k/mistborn/-/wikis/
 Mistborn depends on these core open source technologies:
 - [Docker](https://www.docker.com/why-docker): containerization
- [WireGuard](https://www.wireguard.com): secure VPN access
+- [Wireguard](https://www.wireguard.com): secure VPN access
 - [SSH](https://www.openssh.com): secure remote management
 These tools are not vital to Mistborn itself but are integrated to enhance security, ease, and features:
@@ -62,6 +62,7 @@ Within Mistborn is a panel to enable and manage these free extra services (off b
 # Quickstart
 Tested Operating Systems (in order of thoroughness):
 - Ubuntu 20.04 LTS
 - Ubuntu 18.04 LTS
 - Debian 10 (Buster)
 - Raspberry Pi OS (formerly Raspbian) Buster
@@ -83,7 +84,7 @@ Recommended System Specifications:
 | Use Case               | Description                                                                   | RAM   | Hard Disk |
 |------------------------|-------------------------------------------------------------------------------|-------|-----------|
-| Bare bones             | WireGuard, Pihole (no Cockpit, no extra services)                             | 2 GB  | 15 GB     |
+| Bare bones             | Wireguard, Pihole (no Cockpit, no extra services)                             | 2 GB  | 15 GB     |
 | Default                | Bare bones + Cockpit                                                          | 2 GB+ | 15 GB     |
 | Low-resource services  | Default + Bitwarden, Tor, Syncthing                                           | 4 GB  | 20 GB     |
 | High-resource services | Default + Jitsi, Nextcloud, Jellyfin, Rocket.Chat, Home Assistant, OnlyOffice | 6 GB+ | 25 GB+    |
@@ -95,13 +96,13 @@ git clone https://gitlab.com/cyber5k/mistborn.git
 sudo -E bash ./mistborn/scripts/install.sh
 ```
-Get default admin WireGuard profile
+Get default admin Wireguard profile
 *wait 1 minute after "Mistborn Installed" message*
 ```
 sudo mistborn-cli getconf 
 ```
-Connect via WireGuard then visit `http://home.mistborn`
+Connect via Wireguard then visit `http://home.mistborn`
 For more information, see the [Installation](#installation) section below.
@@ -109,22 +110,17 @@ For more information, see the [Installation](#installation) section below.
 ![Mistborn Network Diagram](https://gitlab.com/cyber5k/public/-/raw/master/graphics/mistborn_network.png)
 Mistborn protects your data in a variety of ways:
- All of your devices are protected wherever they go with the WireGuard VPN protocol
+- All of your devices are protected wherever they go with the Wireguard VPN protocol
 - The Mistborn firewall blocks unsolicited incoming internet packets
 - Pi-hole running on Mistborn blocks outgoing internet requests to configurable blocked domains (ads, malicious/phishing domains, etc.) 
 See the [Mistborn Network Security](https://gitlab.com/cyber5k/mistborn/-/wikis/Mistborn-Network-Security) wiki page to see more network diagrams and the network scan results for Mistborn.
 # Status
 ![Mistborn Home](https://gitlab.com/cyber5k/public/-/raw/master/graphics/home_status.png)
 The home page receives WireGuard status updates from the server via WebSocket connections. Superusers receive detailed updates about all connections and profiles. Regular users see details about their own devices.
 # Security Information & Event Management (SIEM)
 ![Mistborn Security Center](https://gitlab.com/cyber5k/public/-/raw/master/graphics/home.mistborn_soc.png)
-The Mistborn Security Operations Center provides SIEM services with Wazuh. The Wazuh Manager requires an Open Distro for Elasticsearch backend. When the Mistborn host has >8 GB RAM the provided Elasticsearch backend can be used. Just click "Start Wazuh" on the `Security Center` page and enjoy your Enterprise-grade SIEM. Wazuh agents can be installed on just about any OS and all Wazuh agent traffic is communicated over the WireGuard connections. Instructions for adding endpoint agents can be found within Wazuh itself.
+The Mistborn Security Operations Center provides SIEM services with Wazuh. The Wazuh Manager requires an Open Distro for Elasticsearch backend. When the Mistborn host has >8 GB RAM the provided Elasticsearch backend can be used. Just click "Start Wazuh" on the `Security Center` page and enjoy your Enterprise-grade SIEM. Wazuh agents can be installed on just about any OS and all Wazuh agent traffic is communicated over the Wireguard connections. Instructions for adding endpoint agents can be found within Wazuh itself.
 Mistborn's Wazuh installs and integrates with Suricata running on Mistborn with logs ingested into Wazuh.
@@ -148,7 +144,7 @@ We were getting frustrated at being forced to choose between being connected to
 *Netflix blocking my connections that it sees coming from a DigitalOcean droplet*
-In Mistborn, Gateways are upstream from the VPN server so connections to third-party services (e.g. Netflix, Hulu, etc.) will appear to be coming from the public IP address of the Gateway. I setup a Gateway at home (Raspberry Pi with `wireguard` and `openresolv` installed) and with our Mistborn on DigitalOcean, all WireGuard profiles created with this Gateway will appear to be coming from my house and are not blocked. No port-forwarding required (assuming Mistborn is publicly accessible).
+In Mistborn, Gateways are upstream from the VPN server so connections to third-party services (e.g. Netflix, Hulu, etc.) will appear to be coming from the public IP address of the Gateway. I setup a Gateway at home (Raspberry Pi with `wireguard` and `openresolv` installed) and with our Mistborn on DigitalOcean, all Wireguard profiles created with this Gateway will appear to be coming from my house and are not blocked. No port-forwarding required (assuming Mistborn is publicly accessible).
 ![Mistborn Gateway Diagram](https://gitlab.com/cyber5k/public/-/raw/master/graphics/gateway_network.png)
@@ -161,7 +157,7 @@ Mistborn enables remote desktop access via the Apache Guacamole extra service, w
 ![Guacamole Recent Connections](https://gitlab.com/cyber5k/public/-/raw/master/graphics/guacamole_connections.png)
-Guacamole implements its own users and groups access controls to manage access to individual desktops. All Mistborn users must be authenticated with Mistborn (via WireGuard only or MFA) to access the Guacamole interface.
+Guacamole implements its own users and groups access controls to manage access to individual desktops. All Mistborn users must be authenticated with Mistborn (via Wireguard only or MFA) to access the Guacamole interface.
 # Client to client communication
 By default direct communication between network clients is blocked. Mistborn clients can all talk to Mistborn and communicate via shared services (Jitsi, Nextcloud, etc). Direct client to client communication can be enabled via the "client-to-client" toggle.
@@ -169,7 +165,7 @@ By default direct communication between network clients is blocked. Mistborn cli
 ![System Settings](https://gitlab.com/cyber5k/public/-/raw/master/graphics/system_settings_dropdown.png)
 # Installation
-Mistborn is regularly tested on Ubuntu 20.04 LTS (DigitalOcean droplet with 2 GB RAM). It has also been successfully used on Debian Buster and Raspbian Buster systems (though not regularly tested). Make sure to install OS updates and restart before installing Mistborn (WireGuard installs differently on recent kernels).
+Mistborn is regularly tested on Ubuntu 20.04 LTS (DigitalOcean droplet with 2 GB RAM). It has also been successfully used on Debian Buster and Raspbian Buster systems (though not regularly tested). Make sure to install OS updates and restart before installing Mistborn (Wireguard installs differently on recent kernels).
 Clone the git repository and run the install script:
 ```
@@ -184,7 +180,7 @@ Running `install.sh` will do the following:
 - install iptables-persistent
 - install Docker
 - install OpenSSH
- install WireGuard
+- install Wireguard
 - install Cockpit (optional)
 - create a `cockpit` system user (if Cockpit is installed)
 - configure unattended-upgrades
@@ -212,23 +208,23 @@ sudo -E bash -c "source ./mistborn/scripts/noninteractive/.install_barebones &&
 ```
 # Post-Installation
-When Mistborn-base starts up it will create volumes, initialize the PostgreSQL database, start pihole, run Django migrations and then check to see if a Mistborn superuser named `admin` exists yet. If not, it will create the superuser `admin` along with an accompanying default WireGuard configuration file and start the WireGuard service. You can watch all of this happen with:
+When Mistborn-base starts up it will create volumes, initialize the PostgreSQL database, start pihole, run Django migrations and then check to see if a Mistborn superuser named `admin` exists yet. If not, it will create the superuser `admin` along with an accompanying default Wireguard configuration file and start the Wireguard service. You can watch all of this happen with:
 ```
 sudo journalctl -xfu Mistborn-base
 ```
-The default WireGuard configuration file for `admin` may be obtained via:
+The default Wireguard configuration file for `admin` may be obtained via:
 ```
 sudo mistborn-cli getconf 
 ```
-Please notice that the following lines are **NOT** part of the WireGuard config:
+Please notice that the following lines are **NOT** part of the Wireguard config:
 ```
 Starting mistborn_production_postgres ... done
 Starting mistborn_production_redis    ... done
 PostgreSQL is available
 ```
-The WireGuard config will look like this:
+The Wireguard config will look like this:
 ```
 # "10.15.91.2" - WireGuard Client Profile
 [Interface]
@@ -250,18 +246,18 @@ AllowedIPs = 0.0.0.0/0,::/0
 Endpoint = <Mistborn public IP address>:39207
 ```
-## Login via WireGuard
+## Login via Wireguard
-[Install wireguard](https://www.wireguard.com/install/) on your computer. If you get a `resolvconf: command not found` error when starting WireGuard then install openresolv: `sudo apt-get install -y openresolv`
+[Install wireguard](https://www.wireguard.com/install/) on your computer. If you get a `resolvconf: command not found` error when starting Wireguard then install openresolv: `sudo apt-get install -y openresolv`
- Copy the text of the default admin WireGuard config to `/etc/wireguard/wg_admin.conf` on your computer
+- Copy the text of the default admin Wireguard config to `/etc/wireguard/wg_admin.conf` on your computer
 - Run `sudo systemctl start wg-quick@wg_admin`
 - Run `sudo systemctl enable wg-quick@wg_admin`
 - Open your browser and go to "http://home.mistborn"
 - Browse your Mistborn system!
 **Note:** The home.mistborn server takes a minute to come up after Mistborn is up (collectstatic on all that frontend JavaScript and CSS)
-## WireGuard Management
+## Wireguard Management
-Mistborn users can be added (non-privileged or superuser) and removed by superusers. Multiple WireGuard profiles can be created for each user. A non-privileged user can create profiles for themselves.
+Mistborn users can be added (non-privileged or superuser) and removed by superusers. Multiple Wireguard profiles can be created for each user. A non-privileged user can create profiles for themselves.
-![Mistborn WireGuard](https://gitlab.com/cyber5k/public/-/raw/master/graphics/home.mistborn_wireguard_.png)*WireGuard Management in Mistborn*
+![Mistborn Wireguard](https://gitlab.com/cyber5k/public/-/raw/master/graphics/home.mistborn_wireguard_.png)*Wireguard Management in Mistborn*
 ## Extra Services
 Mistborn makes extra services available.
@@ -276,11 +272,11 @@ There are multiple ways to authenticate and use the system.
 ![Mistborn Multi Factor Authentication - Authenticator App Setup](https://gitlab.com/cyber5k/public/-/raw/master/graphics/mfa_qr.png)*Mistborn Multi Factor Authentication - Authenticator App Setup*
-## Profile: WireGuard Authentication
+## Profile: Wireguard Authentication
-Mistborn always authenticates with WireGuard. You must have a valid WireGuard configuration file associated with the correct internal IP address. A classic Mistborn profile (WireGuard Only) will allow you to access the internet and all services hosted by Mistborn once you have connected via WireGuard. Note: individual services may require passwords or additional authentication.
+Mistborn always authenticates with Wireguard. You must have a valid Wireguard configuration file associated with the correct internal IP address. A classic Mistborn profile (Wireguard Only) will allow you to access the internet and all services hosted by Mistborn once you have connected via Wireguard. Note: individual services may require passwords or additional authentication.
 ## Profile: Multi Factor Authentication (MFA)
-In addition to WireGuard, you may create a Mistborn profile enabling multi-factor authentication (MFA). You must first connect to Mistborn via WireGuard. Then all internet traffic will route you to the Mistborn webserver where you must first setup and thereafter authenticate with an app (Google Authenticator, Authy, etc.). You must go to [http://home.mistborn](http://home.mistborn) to complete the authentication process.
+In addition to Wireguard, you may create a Mistborn profile enabling multi-factor authentication (MFA). You must first connect to Mistborn via Wireguard. Then all internet traffic will route you to the Mistborn webserver where you must first setup and thereafter authenticate with an app (Google Authenticator, Authy, etc.). You must go to [http://home.mistborn](http://home.mistborn) to complete the authentication process.
 ![Mistborn Multi Factor Authentication](https://gitlab.com/cyber5k/public/-/raw/master/graphics/mfa1.png)*Mistborn Multi Factor Authentication Prompt*
@@ -298,7 +294,7 @@ Mistborn service access is blocked via traefik until Mistborn authentication is
 - **Sessions**: Traefik checks the authenticated sessions on the server side to determine whether to allow access to the Mistborn service web pages. If an open session exists for your Mistborn IP address then access will be granted. You may close all sessions by clicking "Sign Out" on the Mistborn home page. Expired sessions are regularly cleaned by the Mistborn system (celery periodic task).
 # Mistborn Subdomains
-Mistborn uses the following domains (that can be reached by all WireGuard clients):
+Mistborn uses the following domains (that can be reached by all Wireguard clients):
 | Service | Domain | Default Status |
 | ------- | ------ | -------------- |
@@ -332,14 +328,14 @@ These are the default credentials to use in the services you choose to use:
 You can find the credentials sent to the Docker containers in: `/opt/mistborn/.envs/.production/`
 # Gateway Setup
-Mistborn will generate the WireGuard configuration script for the Gateway. From a base Ubuntu/Debian/Raspbian operating system the following packages are recommended to be installed beforehand:
+Mistborn will generate the Wireguard configuration script for the Gateway. From a base Ubuntu/Debian/Raspbian operating system the following packages are recommended to be installed beforehand:
 ## Gateway Requirements
- WireGuard (you can consult the Mistborn WireGuard installer: `mistborn/scripts/subinstallers/wireguard.sh`)
+- Wireguard (you can consult the Mistborn Wireguard installer: `mistborn/scripts/subinstallers/wireguard.sh`)
- Openresolv (a WireGuard dependency that is also installed via the Mistborn WireGuard installer)
+- Openresolv (a Wireguard dependency that is also installed via the Mistborn Wireguard installer)
 - Fail2ban
-## Install Gateway WireGuard config file
+## Install Gateway Wireguard config file
 On Mistborn:
 - Click `View Config` on the Gateways tab in Mistborn
 - Highlight the config
@@ -351,15 +347,15 @@ On Gateway:
 - Run `sudo systemctl enable wg-quick@gateway`
 # Phones and Mobile Devices
-All your devices can be connected to Mistborn as WireGuard clients.
+All your devices can be connected to Mistborn as Wireguard clients.
 First steps:
-1. Device: Download the WireGuard app on your device. Links: [Android](https://play.google.com/store/apps/details?id=com.wireguard.android) [Apple](https://apps.apple.com/us/app/wireguard/id1441195209)
+1. Device: Download the Wireguard app on your device. Links: [Android](https://play.google.com/store/apps/details?id=com.wireguard.android) [Apple](https://apps.apple.com/us/app/wireguard/id1441195209)
-1. Mistborn: Create a WireGuard profile for the device.
+1. Mistborn: Create a Wireguard profile for the device.
-1. Device: Scan WireGuard client QR code in WireGuard app.
+1. Device: Scan Wireguard client QR code in Wireguard app.
-1. Device: Enable WireGuard connection.
+1. Device: Enable Wireguard connection.
-All of you device network traffic is now being routed through WireGuard. Ads and malicious sites are blocked by pihole. DNS queries are verified via DNScrypt.
+All of you device network traffic is now being routed through Wireguard. Ads and malicious sites are blocked by pihole. DNS queries are verified via DNScrypt.
 But wait, there's more! You can:
 - visit the [Mistborn web interface](http://home.mistborn) through your phone's browser. 
@@ -378,7 +374,7 @@ But wait, there's more! You can:
 | Rocket.Chat    | [Rocket.Chat](https://play.google.com/store/apps/details?id=chat.rocket.android)                   | [Rocket.Chat](https://apps.apple.com/us/app/rocket-chat/id1148741252)              |
 ## TLS Certificate
-Some apps require TLS (HTTPS). All traffic to Mistborn domains already occurs over WireGuard but to keep apps running, a TLS certificate exists for Mistborn and can be imported into your device's trusted credentials in the security settings. This certificate is checked every day and will be re-generated when expiration is less than 30 days away.
+Some apps require TLS (HTTPS). All traffic to Mistborn domains already occurs over Wireguard but to keep apps running, a TLS certificate exists for Mistborn and can be imported into your device's trusted credentials in the security settings. This certificate is checked every day and will be re-generated when expiration is less than 30 days away.
 The TLS certificate can be found here:
 ```
@@ -388,7 +384,7 @@ The TLS certificate can be found here:
 # FAQ
 Frequently Asked Questions
-## Where is my data?
+## Where is My Data?
 The Docker services mount volumes located in:
 ```
@@ -405,11 +401,11 @@ Your data from Nextcloud, Syncthing, Bitwarden, etc. will be located there.
 ## How do I SSH into Mistborn?
 If Mistborn is installed via SSH then an iptables rule is added allowing external SSH connections from the same source IP address only. If Mistborn was installed locally then no external SSH is permitted.
-SSH is permitted from any device connected to Mistborn by WireGuard.
+SSH is permitted from any device connected to Mistborn by Wireguard.
 Password authentication in enabled. Fail2ban blocks IPs with excessive failed login attempts.
-You can SSH using the Mistborn domain when connected by WireGuard:
+You can SSH using the Mistborn domain when connected by Wireguard:
 ```
 ssh user@home.mistborn
 ```
@@ -430,38 +426,9 @@ services:
 The available options are here: https://download.dnscrypt.info/dnscrypt-resolvers/v2/public-resolvers.md
 ## How do I purge an extra service/start fresh?
 This is a manual process for the foreseeable future because it is destructive and cannot be undone. In order to purge an extra service do the following:
 - Stop and disable the service
 This can be done from the Mistborn GUI or:
 ```
 sudo systemctl stop Mistborn-<service name>
 sudo systemctl disable Mistborn-<service name>
 ```
 - Remove the data folder
 Locate the correct folder: `sudo ls -ahl /opt/mistborn_volumes/extra/`
 **Be careful:**
 Now remove the folder: `sudo rm -r /opt/mistborn_volumes/extra/<service name>`
 - Remove the variables file
 Locate the file: `sudo ls -ahl /opt/mistborn/.envs/.production/`
 **Be careful:**
 Now remove the file: `sudo rm /opt/mistborn/.envs/.production/.<service name>`
 Now you can restart the service from the GUI or manually and it should be a first run experience.
 # Troubleshooting
-Once you're connected to WireGuard you should see .mistborn domains and the internet should work as expected. Be sure to use http (http://home.mistborn). WireGuard is the encrypted channel so there's usually no need to bother with TLS certs (WebRTC functionality and some mobile apps require TLS so it is available). Here are some things to check if you have issues:
+Once you're connected to Wireguard you should see .mistborn domains and the internet should work as expected. Be sure to use http (http://home.mistborn). Wireguard is the encrypted channel so there's usually no need to bother with TLS certs (WebRTC functionality and some mobile apps require TLS so it is available). Here are some things to check if you have issues:
 Check if you can ping an external IP address:
 ```
@@ -493,18 +460,18 @@ Mistborn-base is a systemd process and at any time restarting it should get you
 sudo systemctl restart Mistborn-base
 ```
-The WireGuard processes run independently of Mistborn and will still be up if Mistborn is down. You can check running WireGuard interfaces with:
+The Wireguard processes run independently of Mistborn and will still be up if Mistborn is down. You can check running Wireguard interfaces with:
 ```
 sudo wg show
 ```
-Note the Mistborn naming convention for WireGuard interfaces on the server is wg<listening port>. So if the particular WireGuard process is listening on UDP port 56392 then the interface will be named wg56392 and the config will be in `/etc/wireguard/wg56392.conf`
+Note the Mistborn naming convention for Wireguard interfaces on the server is wg<listening port>. So if the particular Wireguard process is listening on UDP port 56392 then the interface will be named wg56392 and the config will be in `/etc/wireguard/wg56392.conf`
 The `dev/` folder contains a script for completing a hard reset: destroying and rebuilding the system from the original backup:
 ```
 sudo ./dev/rebuild.sh
 ```
-## Troubleshooting WireGuard
+## Troubleshooting Wireguard
 Ensure that your public IP address in your client profile (e.g. `Endpoint = <Mistborn public IP address>:<random port>`) is actually publicly available (not in 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16) if you are attempting to access Mistborn across the internet.
 ## Troubleshooting Extra Services
@@ -538,13 +505,13 @@ sudo systemctl restart docker
 ## Troubleshooting Upgrade from Ubuntu 18.04 to 20.04
 New installations of 18.04 and 20.04 after 25 April 2020 don't seem to be having issues. If you installed Mistborn on Ubuntu 18.04 prior to 25 April 2020 and then upgrade to 20.04 you may have one minor issue described below.
-Owing to changes in docker NAT rules and container DNS resolution, some WireGuard client configurations generated with Mistborn before 25 April 2020 (be sure to update Mistborn) may experience issues after upgrading to Ubuntu 20.04 LTS. Symptoms: can ping but can't resolve DNS.
+Owing to changes in docker NAT rules and container DNS resolution, some Wireguard client configurations generated with Mistborn before 25 April 2020 (be sure to update Mistborn) may experience issues after upgrading to Ubuntu 20.04 LTS. Symptoms: can ping but can't resolve DNS.
-Solution: Edit the WireGuard client config and set the DNS directive as follows:
+Solution: Edit the Wireguard client config and set the DNS directive as follows:
 ```
 DNS = 10.2.3.1
 ```
-Close the config and restart the client WireGuard process.
+Close the config and restart the client Wireguard process.
 ## Troubleshooting Raspberry Pi OS (Raspbian)
 Be sure to always reboot after updating the kernel. When the kernel is updated the kernel modules are deleted (for the currently running kernel) and you will have issues with any function requiring kernel modules (e.g. `iptables` or `wireguard`).
@@ -552,7 +519,7 @@ Be sure to always reboot after updating the kernel. When the kernel is updated t
 **Note**: The Raspberry Pi OS 64-bit BETA (versions from May 2020 and prior) have a bug where the os-release info indicates that it is Debian. Mistborn proceeds to install as though it were Debian. Since it's not Debian there are errors.
 ## Troubleshooting Debian 10
-Run updates and restart before installing Mistborn (`sudo apt-get update && sudo apt-get -y dist-upgrade && sudo shutdown -r now`). Some older Linux kernels will prevent newer WireGuard versions from installing.
+Run updates and restart before installing Mistborn (`sudo apt-get update && sudo apt-get -y dist-upgrade && sudo shutdown -r now`). Some older Linux kernels will prevent newer Wireguard versions from installing.
 # Technical and Security Insights
 These are some notes regarding the technical design and implementations of Mistborn. Feel free to contact me for additional details.
@@ -561,15 +528,15 @@ These are some notes regarding the technical design and implementations of Mistb
 See the [Mistborn Network Security](https://gitlab.com/cyber5k/mistborn/-/wikis/Mistborn-Network-Security) wiki entry.
- **WireGuard**: WireGuard is the only way in to Mistborn. When new WireGuard profiles are generated they are attached to a random UDP port. WireGuard does not respond to unauthenticated traffic. External probes on the active WireGuard listening ports are not logged and do not appear on the Metrics page.
+- **Wireguard**: Wireguard is the only way in to Mistborn. When new Wireguard profiles are generated they are attached to a random UDP port. Wireguard does not respond to unauthenticated traffic. External probes on the active Wireguard listening ports are not logged and do not appear on the Metrics page.
- **SSH**: If Mistborn is installed over SSH (most common) then an iptables rule is added allowing future SSH connections from the same source IP address. All other external SSH is blocked. Internal SSH (over the WireGuard tunnels) is allowed. Password authentication is allowed. The SSH key for the `mistborn` user is only accepted from internal source IP addresses. Fail2ban is also installed.
+- **SSH**: If Mistborn is installed over SSH (most common) then an iptables rule is added allowing future SSH connections from the same source IP address. All other external SSH is blocked. Internal SSH (over the Wireguard tunnels) is allowed. Password authentication is allowed. The SSH key for the `mistborn` user is only accepted from internal source IP addresses. Fail2ban is also installed.
- **Traefik**: Iptables closes web ports (TCP 80 and 443) from external access and additonally all web interfaces are behind the Traefik reverse-proxy. All web requests (e.g. home.mistborn) must be resolved by Mistborn DNS (Pihole/dnsmasq) and originate from a WireGuard tunnel.
+- **Traefik**: Iptables closes web ports (TCP 80 and 443) from external access and additonally all web interfaces are behind the Traefik reverse-proxy. All web requests (e.g. home.mistborn) must be resolved by Mistborn DNS (Pihole/dnsmasq) and originate from a Wireguard tunnel.
 - **Docker**: When Docker exposes a port it creates a PREROUTING rule in the NAT table to catch eligible network requests. This means that even if your INPUT chain policy is DROP, your docker containers with exposed ports can receive and respond to traffic. Whenever Mistborn brings up a docker container with an exposed port it creates an iptables rule to block external traffic to that service. 
 ## Firewall
 - **IPtables**: Iptables rules and chains are manipulated directly. If UFW is present it is disabled. IPtables-persistent is used to save a simple set of secure default rules (most importantly setting the INPUT and FORWARD policies to DROP and allowing ESTABLISHED and RELATED traffic) that will be effective immediately upon system startup. Additional rules and chains are created by Docker on startup. Mistborn also creates some iptables chains during installation that are saved in the persistent rules. Mistborn iptables chains and rules are designed to work with Docker's with logic that is easy to follow. A power cycle will always result in a working state.
- **PostUp/PostDown**: WireGuard configuration files on Mistborn include PostUp and PostDown directives that set routes and iptables rules for each WireGuard client individually.
+- **PostUp/PostDown**: Wireguard configuration files on Mistborn include PostUp and PostDown directives that set routes and iptables rules for each Wireguard client individually.
- **WireGuard**: There is a one-to-one mapping between each WireGuard client and server instance listening on Mistborn. By default WireGuard clients cannot talk directly to each other but can use shared services and resources on Mistborn (e.g. Syncthing, Nextcloud, Jitisi, etc). Toggling the "client-to-client" option will enable direct client-to-client communication.
+- **Wireguard**: There is a one-to-one mapping between each Wireguard client and server instance listening on Mistborn. By default Wireguard clients cannot talk directly to each other but can use shared services and resources on Mistborn (e.g. Syncthing, Nextcloud, Jitisi, etc). Toggling the "client-to-client" option will enable direct client-to-client communication.
 - **Metrics**: In addition to the iptables INPUT policy set to DROP, an iptables chain exists that logs the packet meta data before dropping it. Mistborn redirects packets that will be dropped to this chain instead. A summary of the data about these dropped packets (unsolicited network traffic) can be found on the Metrics page.
 - **Coppercloud**: Coppercloud works by populating ipsets with the ipset module in iptables to DROP (blacklist) or ACCEPT (whitelist) a given set of IP addresses. Upon system startup a celery task will compile the IP addresses, create the ipsets, and iptables rules.
@@ -605,7 +572,6 @@ Contact me at [steven@cyber5k.com](mailto:steven@cyber5k.com)
 # Support Mistborn
 Please consider supporting the project via:
 - [Patreon](https://www.patreon.com/cyber5k)
 - [Paypal.me](https://paypal.me/cyber5k)
 - [Buy me a drink](https://www.buymeacoffee.com/cyber5k)
- Bitcoin: `3Lqxc1vpndN3TGi9cipNHg1RgXxGxVDdZo`
+- [Patreon](https://www.patreon.com/cyber5k)
@@ -13,7 +13,7 @@ services:
      - postgres
      - redis
    ports:
-      - "${MISTBORN_DNS_BIND_IP}:5000:5000/tcp" # auth access
+      - "10.2.3.1:5000:5000/tcp" # auth access
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.django-http.rule=Host(`home.mistborn`)"
@@ -51,8 +51,15 @@ services:
    #  context: .
    #  dockerfile: ./compose/production/traefik/Dockerfile
    #image: mistborn_production_traefik
-    image: traefik:v2.4.9
+    image: traefik:v2.2
    container_name: mistborn_production_traefik
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.api.rule=Host(`traefik.mistborn`)"
      - "traefik.http.routers.api.service=api@internal"
      - "traefik.http.routers.api.middlewares=mistborn_headers@file"
      - "traefik.http.routers.api.entrypoints=web"
      #- "traefik.http.services.internal.loadbalancer.server.port=5000"
    depends_on:
      - django
    volumes:
@@ -67,11 +74,11 @@ services:
    #  #- "0.0.0.0:8080:8080/tcp" # dashboard
    command:
      ## API settings
-      #- --api.insecure=true
+      - --api.insecure=true
-      #- --api.dashboard=true
+      - --api.dashboard=true
-      #- --api.debug=true
+      - --api.debug=true
      ## Logs
-      - --log.level=ERROR
+      - --log.level=INFO
      ## Providers
      - --providers.docker=true
      - --providers.docker.exposedbydefault=false
@@ -84,42 +91,8 @@ services:
      #- --serversTransport.insecureSkipVerify=true
    restart: unless-stopped
  portal:
    build:
      context: ./compose/production/portal/
      dockerfile: Dockerfile
    image: mistborn_production_portal
    container_name: mistborn_production_portal
    ports:
      - "${MISTBORN_DNS_BIND_IP}:5001:80"
    environment:
      - SERVER_REDIRECT=home.mistborn
    # optionally define path to redirect all requests
    # if not set nginx var $request_uri is used
      - SERVER_REDIRECT_PATH=/
    # optionally define schema to redirect all requests
    # if not set but X-Forwarded-Proto is send as request header with value 'https' this will be used.
    # In all other cases nginx var `$scheme` is used
    #- SERVER_REDIRECT_SCHEME=https
    # optionally define the http code to use for redirection
    # allowed Codes are: 301, 302, 303, 307, 308, default is 301
    #- SERVER_REDIRECT_CODE=301
    # optionally define the http code to redirect POST requests
    # if not set or not in allowed Codes, SERVER_REDIRECT_CODE will be used
    #- SERVER_REDIRECT_POST_CODE=
    # optionally define the http code to redirect PUT, PATCH and DELETE requests
    # if not set or not in allowed Codes, SERVER_REDIRECT_CODE will be used
    #- SERVER_REDIRECT_PUT_PATCH_DELETE_CODE=
    # optionally define the location for the nginx access log
    # if not set /dev/stdout is used
    #- SERVER_ACCESS_LOG=/dev/null
    # optionally define the location for the nginx error log
    # if not set /dev/stderr is used
    #- SERVER_ERROR_LOG=/dev/null
    restart: unless-stopped
  redis:
-    image: redis:6.2-alpine
+    image: redis:5.0
    container_name: mistborn_production_redis
    restart: unless-stopped
@@ -138,10 +111,8 @@ services:
      default:
      dns_net:
        ipv4_address: 10.2.1.3
        ipv6_address: "fd0c:6164:c111:ecee::3"
    dns:
      - 10.2.1.2
      - "fd0c:6164:c111:ecee::2"
    depends_on:
      - traefik
      - pihole
@@ -163,10 +134,8 @@ services:
      default:
      dns_net:
        ipv4_address: 10.2.1.4
        ipv6_address: "fd0c:6164:c111:ecee::4"
    dns:
      - 10.2.1.2
      - "fd0c:6164:c111:ecee::2"
    depends_on:
      - traefik
      - pihole
@@ -196,7 +165,7 @@ services:
  pihole:
   container_name: mistborn_production_pihole
-   image: pihole/pihole:v5.8
+   image: pihole/pihole:v5.7
   env_file:
     - ./.envs/.production/.pihole
   ports:
@@ -206,20 +175,21 @@ services:
      - "traefik.enable=true"
      - "traefik.http.routers.pihole-http.rule=Host(`pihole.mistborn`)"
      - "traefik.http.routers.pihole-http.entrypoints=web"
-      - "traefik.http.routers.pihole-http.middlewares=mistborn_auth@file,add-pihole-admin"
+      - "traefik.http.routers.pihole-http.middlewares=mistborn_auth,add-pihole-admin"
      - "traefik.http.routers.pihole-https.rule=Host(`pihole.mistborn`)"
      - "traefik.http.routers.pihole-https.entrypoints=websecure"
-      - "traefik.http.routers.pihole-https.middlewares=mistborn_auth@file,add-pihole-admin"
+      - "traefik.http.routers.pihole-https.middlewares=mistborn_auth,add-pihole-admin"
      - "traefik.http.routers.pihole-https.tls.certresolver=basic"
      - "traefik.http.middlewares.add-pihole-admin.addPrefix.prefix=/admin"
      - "traefik.http.services.pihole-service.loadbalancer.server.port=80"
      - "traefik.http.middlewares.mistborn_auth.forwardAuth.address=http://${MISTBORN_BIND_IP}:5000/auth/"
      - "traefik.http.middlewares.mistborn_auth.forwardAuth.trustForwardHeader=true"
      - "traefik.http.middlewares.mistborn_auth.forwardAuth.tls.insecureSkipVerify=true"
   environment:
     - ServerIP=10.2.0.3
-     - PIHOLE_DNS_=10.2.0.2#5054;fdce:7a9e:13ce:d817::2#5054
+     - DNS1='10.2.0.2#5054' # docs say port 5054, was 54; use network_mode: host to see which port is used
-     - ServerIPv6=fdce:7a9e:13ce:d817::3
+     - DNS2=''
-     #- DNS1='10.2.0.2#5054' # docs say port 5054, was 54; use network_mode: host to see which port is used
+     - IPv6='false'
     #- DNS2=''
     - IPv6=true
     - DNSMASQ_LISTENING=all
   #  TZ: 'America/New York'
   # Volumes store your data between container upgrades
@@ -232,10 +202,8 @@ services:
     default:
     pihole_net:
       ipv4_address: 10.2.0.3
       ipv6_address: "fdce:7a9e:13ce:d817::3"
     dns_net:
       ipv4_address: 10.2.1.2
       ipv6_address: "fd0c:6164:c111:ecee::2"
   restart: unless-stopped
  dnscrypt-proxy:
@@ -249,34 +217,17 @@ services:
    networks:
      pihole_net:
        ipv4_address: 10.2.0.2
        ipv6_address: "fdce:7a9e:13ce:d817::2"
    restart: unless-stopped
 networks:
  default:
    driver: bridge
    driver_opts:
      com.docker.network.enable_ipv6: "true"
    ipam:
      config:
        - subnet: "fd39:4459:ffa9:a36f::/64"
  pihole_net:
    driver: bridge
    driver_opts:
      com.docker.network.enable_ipv6: "true"
    ipam:
      config:
        - subnet: 10.2.0.0/29
        - subnet: "fdce:7a9e:13ce:d817::/64"
  dns_net:
    driver: bridge
    driver_opts:
      com.docker.network.enable_ipv6: "true"
    ipam:
      config:
        - subnet: 10.2.1.0/24
        - subnet: "fd0c:6164:c111:ecee::/64"
@@ -1,8 +0,0 @@
 FROM nginx:1.21.1-alpine
 ADD run.sh /run.sh
 ADD default.conf /etc/nginx/conf.d/default.conf
 RUN chmod +x /run.sh
 CMD ["/run.sh"]
@@ -1,29 +0,0 @@
 map $http_x_forwarded_proto $redirect_scheme {
    default $scheme;
    https https;
 }
 server {
    listen       80;
    listen       [::]:80;
    server_name  ${SERVER_NAME};
    # cherry picked from https://github.com/schmunk42/docker-nginx-redirect/pull/8
    if ($request_method = POST) {
        return ${SERVER_REDIRECT_POST_CODE} ${SERVER_REDIRECT_SCHEME}://${SERVER_REDIRECT}${SERVER_REDIRECT_PATH};
    }
    if ($request_method ~ PUT|PATCH|DELETE) {
        return ${SERVER_REDIRECT_PUT_PATCH_DELETE_CODE} ${SERVER_REDIRECT_SCHEME}://${SERVER_REDIRECT}${SERVER_REDIRECT_PATH};
    }
    return ${SERVER_REDIRECT_CODE} ${SERVER_REDIRECT_SCHEME}://${SERVER_REDIRECT}${SERVER_REDIRECT_PATH};
    # redirect server error pages to the static page /50x.html
    #
    error_page   500 502 503 504  /50x.html;
    location = /50x.html {
        root   /usr/share/nginx/html;
    }
 }
@@ -1,54 +0,0 @@
 #!/usr/bin/env sh
 if [ ! -n "$SERVER_REDIRECT" ] ; then
    echo "Environment variable SERVER_REDIRECT is not set, exiting."
    exit 1
 fi
 # set server name from optional ENV var
 if [ ! -n "$SERVER_NAME" ] ; then
    SERVER_NAME='localhost'
 fi
 # set redirect code from optional ENV var
 # allowed Status Codes are: 301, 302, 303, 307, 308
 expr match "$SERVER_REDIRECT_CODE" '30[12378]$' > /dev/null || SERVER_REDIRECT_CODE='301'
 # set redirect code from optional ENV var for POST requests
 expr match "$SERVER_REDIRECT_POST_CODE" '30[12378]$' > /dev/null || SERVER_REDIRECT_POST_CODE=$SERVER_REDIRECT_CODE
 # set redirect code from optional ENV var for PUT, PATCH and DELETE requests
 expr match "$SERVER_REDIRECT_PUT_PATCH_DELETE_CODE" '30[12378]$' > /dev/null || SERVER_REDIRECT_PUT_PATCH_DELETE_CODE=$SERVER_REDIRECT_CODE
 # set redirect path from optional ENV var
 if [ ! -n "$SERVER_REDIRECT_PATH" ] ; then
    SERVER_REDIRECT_PATH='$request_uri'
 fi
 # set redirect scheme from optional ENV var
 if [ ! -n "$SERVER_REDIRECT_SCHEME" ] ; then
    SERVER_REDIRECT_SCHEME='$redirect_scheme'
 fi
 # set access log location from optional ENV var
 if [ ! -n "$SERVER_ACCESS_LOG" ] ; then
    SERVER_ACCESS_LOG='/dev/stdout'
 fi
 # set error log location from optional ENV var
 if [ ! -n "$SERVER_ERROR_LOG" ] ; then
    SERVER_ERROR_LOG='/dev/stderr'
 fi
 sed -i "s|\${SERVER_REDIRECT}|${SERVER_REDIRECT}|" /etc/nginx/conf.d/default.conf
 sed -i "s|\${SERVER_NAME}|${SERVER_NAME}|" /etc/nginx/conf.d/default.conf
 sed -i "s|\${SERVER_REDIRECT_CODE}|${SERVER_REDIRECT_CODE}|" /etc/nginx/conf.d/default.conf
 sed -i "s|\${SERVER_REDIRECT_POST_CODE}|${SERVER_REDIRECT_POST_CODE}|" /etc/nginx/conf.d/default.conf
 sed -i "s|\${SERVER_REDIRECT_PUT_PATCH_DELETE_CODE}|${SERVER_REDIRECT_PUT_PATCH_DELETE_CODE}|" /etc/nginx/conf.d/default.conf
 sed -i "s|\${SERVER_REDIRECT_PATH}|${SERVER_REDIRECT_PATH}|" /etc/nginx/conf.d/default.conf
 sed -i "s|\${SERVER_REDIRECT_SCHEME}|${SERVER_REDIRECT_SCHEME}|" /etc/nginx/conf.d/default.conf
 ln -sfT "$SERVER_ACCESS_LOG" /var/log/nginx/access.log
 ln -sfT "$SERVER_ERROR_LOG" /var/log/nginx/error.log
 exec nginx -g 'daemon off;'
@@ -1,4 +1,4 @@
-FROM postgres:13.3-alpine
+FROM postgres:11.3
 COPY ./compose/production/postgres/maintenance /usr/local/bin/maintenance
 RUN chmod +x /usr/local/bin/maintenance/*
@@ -1,4 +1,4 @@
-FROM alpine:3.14.0
+FROM alpine:latest
 RUN apk update \
 && apk upgrade \
@@ -1,4 +1,4 @@
-FROM traefik:v2.4.9
+FROM traefik:v2.2
 RUN mkdir -p /etc/traefik/acme
 RUN touch /etc/traefik/acme/acme.json
 RUN chmod 600 /etc/traefik/acme/acme.json
@@ -11,21 +11,15 @@
 [http.services]
  [http.services.cockpit.loadBalancer]
    [[http.services.cockpit.loadBalancer.servers]]
-      url = "http://10.2.3.1:9090"
+      url = "http://127.0.0.1:9090"
 [http.routers]
  [http.routers.cockpit]
    rule = "Host(`cockpit.mistborn`)"
    service = "cockpit"
    entrypoints = ["web", "websecure"]
-    middlewares = ["mistborn_auth"]
+    middlewares = ["mistborn_auth@docker"]
 [http.middlewares]
  [http.middlewares.mistborn_auth.forwardAuth]
    address = "http://10.2.3.1:5000/auth/"
    trustForwardHeader = true
    [http.middlewares.mistborn_auth.forwardAuth.tls]
      insecureSkipVerify = true
  [http.middlewares.mistborn_headers.headers]
    hostsProxyHeaders = ['X-CSRFToken']
@@ -2,7 +2,7 @@ version: '3'
 services:  
  bitwarden:
-    image: vaultwarden/server:latest
+    image: bitwardenrs/server:latest
    container_name: mistborn_production_bitwarden
    env_file:
      - ../.envs/.production/.bitwarden
@@ -3,7 +3,7 @@ version: '3.7'
 services:
  elasticsearch:
-    image: amazon/opendistro-for-elasticsearch:1.13.2
+    image: amazon/opendistro-for-elasticsearch:1.12.0
    hostname: elasticsearch
    restart: unless-stopped
    ports:
@@ -5,7 +5,7 @@ services:
  # guacd
  guacd:
    container_name: mistborn_production_guacd
-    image: guacamole/guacd:1.3.0
+    image: guacamole/guacd
    networks:
      guacnetwork:
    restart: unless-stopped
@@ -53,7 +53,7 @@ services:
      #GUACAMOLE_HOME: /config
    env_file:
    - ../.envs/.production/.guacamole
-    image: guacamole/guacamole:1.3.0
+    image: guacamole/guacamole
    links:
    - guacd
    networks:
@@ -2,7 +2,7 @@ version: '3'
 services:
  syncthing:
-    image: linuxserver/syncthing:latest
+    image: linuxserver/syncthing
    container_name: mistborn_production_syncthing
    environment:
      - PUID=1000
@@ -3,7 +3,7 @@ version: '3.7'
 services:
  wazuh:
-    image: wazuh/wazuh-odfe:4.1.5
+    image: wazuh/wazuh-odfe:4.1.2
    hostname: wazuh-manager
    restart: unless-stopped
    ports:
@@ -29,7 +29,7 @@ services:
      - filebeat_var:/var/lib/filebeat
  wazuh-kibana:
-    image: wazuh/wazuh-kibana-odfe:4.1.5
+    image: wazuh/wazuh-kibana-odfe:4.1.2
    hostname: wazuh-kibana
    restart: unless-stopped
    labels:
@@ -11,11 +11,6 @@ mkdir -p /opt/mistborn_volumes/extra/elasticsearch/init/ >/dev/null 2>&1
 chmod -R +x /opt/mistborn_volumes/extra/elasticsearch/init/
 cp /opt/mistborn/scripts/services/elasticsearch/files/internal_users.yml /opt/mistborn_volumes/extra/elasticsearch/init/
-ELASTICSEARCH_MISTBORN_HASHED="$(docker run --rm amazon/opendistro-for-elasticsearch:1.12.0 bash /usr/share/elasticsearch/plugins/opendistro_security/tools/hash.sh -p ${MISTBORN_DEFAULT_PASSWORD} | tr -d '\n')"
+ELASTICSEARCH_MISTBORN_HASHED=$(docker run --rm amazon/opendistro-for-elasticsearch:1.12.0 bash /usr/share/elasticsearch/plugins/opendistro_security/tools/hash.sh -p ${MISTBORN_DEFAULT_PASSWORD} | tr -d '\n')
 if [[ -z "${ELASTICSEARCH_MISTBORN_HASHED}" ]]; then 
    echo "Elasticsearch password hash not generated properly"
    exit 1;
 fi
 sed -i "s|__MISTBORN_HASH__|${ELASTICSEARCH_MISTBORN_HASHED}|" /opt/mistborn_volumes/extra/elasticsearch/init/internal_users.yml
@@ -1,54 +0,0 @@
 #!/bin/bash
 HASS_CONFIG="/opt/mistborn_volumes/extra/homeassistant/config/configuration.yaml"
 if [[ -f "$HASS_CONFIG" ]]; then
    # configuration.yaml exists
    if [[ ! -z $(grep "use_x_forwarded_for: true" "$HASS_CONFIG") ]]; then
        # FOUND
        exit 0;
    fi
 # add the proxy config
 # write the trusted proxies config
 cat >> ${HASS_CONFIG}<< EOF
 http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 172.16.0.0/12 
 EOF
 exit 0;
 fi
 # create parent directory if needed
 PARENTDIR="$(dirname $HASS_CONFIG)"
 if [[ ! -d "$PARENTDIR" ]]; then
    mkdir -p $PARENTDIR
 fi
 # write the trusted proxies config
 cat >> ${HASS_CONFIG}<< EOF
 # Configure a default setup of Home Assistant (frontend, api, etc)
 default_config:
 # Text to speech
 #tts:
 #  - platform: google_translate
 #group: !include groups.yaml
 #automation: !include automations.yaml
 #script: !include scripts.yaml
 #scene: !include scenes.yaml
 http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 172.16.0.0/12  
 EOF
@@ -6,18 +6,7 @@ figlet "Mistborn: Installing Docker"
 sudo apt update
 sudo -E apt install -y python python3-pip python3-setuptools libffi-dev python3-dev libssl-dev
-# Ubuntu version >= 20.04
+if [ "$DISTRO" == "ubuntu" ] && [ "$VERSION_ID" == "20.04" ]; then
 set +e
 vercomp "$VERSION_ID" "19.10"
 case $? in
    0) op='=';;
    1) op='>';;
    2) op='<';;
 esac
 set -e
 if [ "$DISTRO" == "ubuntu" ] && [ "$op" == ">" ]; then
    echo "Automated Docker install"
    sudo -E apt-get install -y docker-compose
 else
@@ -42,5 +42,3 @@ if [ $? -eq 0 ]; then
    sudo dpkg -i libseccomp2_2.5.1-1_$(dpkg --print-architecture).deb
    popd
 fi
 set -e
@@ -21,8 +21,8 @@ echo "#MAILGUN_API_KEY=" >> $DJANGO_PROD_FILE
 echo "#MAILGUN_API_URL=" >> $DJANGO_PROD_FILE
 echo "#SENTRY_DNS=" >> $DJANGO_PROD_FILE
 echo "MISTBORN_INSTALL_COCKPIT=$MISTBORN_INSTALL_COCKPIT" >> $DJANGO_PROD_FILE
-#echo "MISTBORN_PORTAL_IP=10.2.3.1" >> $DJANGO_PROD_FILE
+echo "MISTBORN_PORTAL_IP=10.2.3.1" >> $DJANGO_PROD_FILE
-echo "MISTBORN_PORTAL_REDIRECT_PORT=5001" >> $DJANGO_PROD_FILE
+echo "MISTBORN_PORTAL_PORT=5000" >> $DJANGO_PROD_FILE
 chmod 600 $DJANGO_PROD_FILE
 # generate production .env file for postgresql
@@ -11,9 +11,6 @@ if [ "$DISTRO" == "ubuntu" ]; then
    sudo systemctl disable ufw || true
 fi
 # make sure user land binaries installed
 sudo apt-get install -y iptables
 # default interface
 iface=$(ip -o -4 route show to default | egrep -o 'dev [^ ]*' | awk 'NR==1{print $2}')
@@ -50,12 +47,8 @@ sudo iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
 if [ ! -z "${SSH_CLIENT}" ]; then
    SSH_SRC=$(echo $SSH_CLIENT | awk '{print $1}')
    SSH_PRT=$(echo $SSH_CLIENT | awk '{print $3}')
    if [[ $SSH_SRC =~ .*:.* ]]; then
        sudo ip6tables -A INPUT -p tcp -s $SSH_SRC --dport $SSH_PRT -j ACCEPT
    else
    sudo iptables -A INPUT -p tcp -s $SSH_SRC --dport $SSH_PRT -j ACCEPT
 fi
 fi
 # docker rules
 sudo iptables -N MISTBORN_DOCKER_INPUT
@@ -95,15 +88,6 @@ echo "Setting ip6tables rules"
 sudo ip6tables -P INPUT ACCEPT
 sudo ip6tables -I INPUT -i lo -j ACCEPT
 sudo ip6tables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
 # Allow as per RFC 4890
 sudo ip6tables -A INPUT -p ipv6-icmp --icmpv6-type 1   -j ACCEPT
 sudo ip6tables -A INPUT -p ipv6-icmp --icmpv6-type 2   -j ACCEPT
 sudo ip6tables -A INPUT -p ipv6-icmp --icmpv6-type 3   -j ACCEPT
 sudo ip6tables -A INPUT -p ipv6-icmp --icmpv6-type 4   -j ACCEPT
 sudo ip6tables -A INPUT -p ipv6-icmp --icmpv6-type 133 -j ACCEPT
 sudo ip6tables -A INPUT -p ipv6-icmp --icmpv6-type 134 -j ACCEPT
 sudo ip6tables -A INPUT -p ipv6-icmp --icmpv6-type 135 -j ACCEPT
 sudo ip6tables -A INPUT -p ipv6-icmp --icmpv6-type 136 -j ACCEPT
 sudo ip6tables -A INPUT -j MISTBORN_LOG_DROP
 sudo ip6tables -P INPUT DROP
@@ -15,39 +15,3 @@ fi
 figlet "UNAME: $UNAME"
 figlet "DISTRO: $DISTRO"
 figlet "VERSION: $VERSION_ID"
 vercomp () {
    # case $? in
    #     0) op='=';;
    #     1) op='>';;
    #     2) op='<';;
    if [[ $1 == $2 ]]
    then
        return 0
    fi
    local IFS=.
    local i ver1=($1) ver2=($2)
    # fill empty fields in ver1 with zeros
    for ((i=${#ver1[@]}; i<${#ver2[@]}; i++))
    do
        ver1[i]=0
    done
    for ((i=0; i<${#ver1[@]}; i++))
    do
        if [[ -z ${ver2[i]} ]]
        then
            # fill empty fields in ver2 with zeros
            ver2[i]=0
        fi
        if ((10#${ver1[i]} > 10#${ver2[i]}))
        then
            return 1
        fi
        if ((10#${ver1[i]} < 10#${ver2[i]}))
        then
            return 2
        fi
    done
    return 0
 }
@@ -1,16 +1,16 @@
 #!/bin/bash
-figlet "Mistborn: Installing WireGuard"
+figlet "Mistborn: Installing Wireguard"
 # if wireguard not in current repositories
 if ! $(sudo apt-cache show wireguard > /dev/null 2>&1) ; then
    # install PPAs
-    echo "Adding WireGuard PPAs"
+    echo "Adding Wireguard PPAs"
    # Wireguard
    if [ "$DISTRO" == "raspbian" ] || [ "$DISTRO" == "raspios" ]; then
-        echo "Adding WireGuard repo keys"
+        echo "Adding Wireguard repo keys"
        sudo -E apt-get install -y dirmngr
        sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 8B48AD6246925553
        sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 7638D0442B90D010
@@ -28,6 +28,6 @@ if ! $(sudo apt-cache show wireguard > /dev/null 2>&1) ; then
    fi
 fi
-echo "Installing WireGuard"
+echo "Installing Wireguard"
 sudo apt-get update
 sudo -E apt-get install -y openresolv wireguard
Author	SHA1	Message	Date
Steven Foerster	3267aaf3de	middleware	2021-05-31 15:08:52 -04:00
Steven Foerster	86c2526512	cockpit	2021-05-31 14:59:16 -04:00
Steven Foerster	bfd44f504f	pihole forwardauth	2021-05-31 14:54:06 -04:00
Steven Foerster	906205aa8e	mistborn auth	2021-05-31 14:20:50 -04:00
Steven Foerster	7a1dab435f	traefik dashboard	2021-05-31 12:01:00 -04:00