From 12f7ba8578febecc6f58fad1ade9c351662eb0cf Mon Sep 17 00:00:00 2001 From: Ikko Eltociear Ashimine Date: Mon, 23 Sep 2024 03:05:07 +0900 Subject: [PATCH] [skip ci] docs: update readme.md (#326) succeptible -> susceptible --- readme.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/readme.md b/readme.md index 85196947..6a6ef168 100644 --- a/readme.md +++ b/readme.md @@ -132,7 +132,7 @@ Another example: ![diag_SN](./diag_SN.png) -Additionally, because every new self-hosted applications re-implement **crucial systems** such as authentication **from scratch** everytime, the **large majority** of them are very succeptible to being **hacked without too much trouble**. This is very bad because not only Docker containers are not isolated, but they also run as **root** by default, which means it can **easily be used** to offer access to your entire server or even infrastructure. +Additionally, because every new self-hosted applications re-implement **crucial systems** such as authentication **from scratch** everytime, the **large majority** of them are very susceptible to being **hacked without too much trouble**. This is very bad because not only Docker containers are not isolated, but they also run as **root** by default, which means it can **easily be used** to offer access to your entire server or even infrastructure. Most tools currently used to self-host **not specifically designed to be secure for your scenario**. Entreprise tools such as Traefik, NGinx, etc... Are designed for different use-cases that assume that the code you are running behind them is **trustworthy**. But who knows what server apps you might be running? On top of that, a lot of reverse-proxies and security tools lock important security features behind 3 to 4 figures business subscriptions that are not realistic for self-hosting.