sad/segfault
1
0
Fork 0
mirror of https://github.com/hackerschoice/segfault.git synced 2024-06-30 18:51:22 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'main' of github.com:hackerschoice/l0pht

Browse Source
This commit is contained in:
rootTHC 2022-03-05 17:28:02 +00:00
commit 287beec80e
1 changed files with 13 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
README.md
View File

@ -3,19 +3,22 @@
Regional Cluster design:
```mermaid
graph TD;
Shell1-->Host1;
Shell2-->Host1;
Shell3-->Host2;
Shell4-->Host2;
Shell5-->Host2;
Host1-->OpenVPN;
Host2-->OpenVPN;
OpenVPN -- Leaving Cluster -->NordVPN
DockerShell1-->DockerSSHD1;
DockerShell2-->DockerSSHD1;
DockerShell3-->DockerSSHD2;
DockerShell4-->DockerSSHD2;
DockerShell5-->DockerSSHD2;
DockerSSHD1-->Server1;
DockerSSHD2-->Server2;
Server1-- Optional VPN -->OpenVPN;
Server2-- Optional VPN -->OpenVPN;
OpenVPN -- Leaving Region -->NordVPN
NordVPN-->INTERNETZ
```
1. Host[12] are running SSHD with special shell that spawns a docker-shell for every new connection.
1. Host run vagrant VM???
1. Server is running OpenSSH in a docker and shares /var/run/docker.sock with the OpenSSH-Docker instance. This allows to have just the docker_cli to be installed and spin up a shell for the user without having to run an extra docker-daemon (but using the docker-daemon from Server instead).
1. On small deployments the ```OpenVPN Server``` can be the same as Server[12]. This allows to run *everything* off 1 single server.
1. AWS Fargate could be utilized by nesting the entire setup in a Docker-in-Docker (dind) configuration.
Cluster can be deployed in various regions for less latency.