Go to file
2022-09-18 19:56:37 +01:00
config/etc cleanup 2022-09-18 12:42:52 +01:00
encfs cleanup 2022-09-18 12:42:52 +01:00
gsnc cleanup 2022-09-18 12:42:52 +01:00
guest cleanup 2022-09-18 12:42:52 +01:00
host cleanup 2022-09-18 12:42:52 +01:00
nordvpn sshfs & sftp. Restricted server. FW 2022-09-09 15:19:46 +01:00
provision cleanup 2022-09-18 12:42:52 +01:00
router cleanup 2022-09-18 12:42:52 +01:00
sfbin better-semaphore-handling 2022-08-02 11:07:05 +01:00
tor cleanup 2022-09-18 12:42:52 +01:00
docker-compose.yml cleanup 2022-09-18 12:42:52 +01:00
Makefile cleanup 2022-09-18 12:42:52 +01:00
README.md Update README.md 2022-09-18 19:56:37 +01:00

segfault.net - A Server Centre Depoyment

This page is for server administrators and those folks who like to run their own Segfault.net Server Centre (SSC). Running your own SSC allows you to offer root-servers to other users.

If this is not what you want and you just like to get a root-shell on your own server then please go to https://www.thc.org/segfault or try our demo deployment:

ssh root@segfault.net # the password is 'segfault'

Deploy a Server Centre:

git clone --depth 1 https://github.com/hackerschoice/segfault.git && \
cd segfault && \
docker build -t sf-guest guest && \
SF_SEED="$(head -c 1024 /dev/urandom | tr -dc '[:alpha:]' | head -c 32)" && \
echo "SF_SEED=${SF_SEED}" && \
SF_BASEDIR=$(pwd) SF_SEED=${SF_SEED} SF_SSH_PORT=2222 docker-compose up

Then log in to a new root server

ssh -p 2222 root@127.1 # password is 'segfault'

Every new SSH connection creates a new dedicated root server.

To stop press Ctrl-C and execute:

docker-compose down

To start execute:

SF_BASEDIR=$(pwd) SF_SEED=SecretFromAbove SF_SSH_PORT=2222 docker-compose up

Take a look at provision/env.example for a sample .env file. Configure the test of the variables in config/etc/sf/sf.conf.

Provisioning

Provisioning turns a freshly created Linux (a bare minimum Installation) into a SSC. It's how we 'ready' a newly launched AWS Instance for SSC deployment. You likely dont ever need this but we wrote it down anyway.


BETA TESTING BETA TESTING

Please report back

  1. Tools missing
  2. Features needed

Some suggestions by others:

  1. Allow user to share data via webserver accessible by normal Internet and TOR (.onion) [thanks 0xD1G, L]
  2. Allow email access [thanks L]
  3. Proxychain [thanks DrWho]
  4. PM me if you have more suggestions

SSC can be deployed in various regions using Route53 to reduce latency.

Helpful links

  1. https://github.com/nicolaka/netshoot
  2. https://www.linuxserver.io/ and https://github.com/just-containers/s6-overlay
  3. https://jordanelver.co.uk/blog/2019/06/03/routing-docker-traffic-through-a-vpn-connection/
  4. https://hub.docker.com/r/alexaso/dnsmasq-dnscrypt and https://github.com/crazy-max/docker-cloudflared
  5. https://wiki.archlinux.org/title/EncFS
  6. https://www.supertechcrew.com/wetty-browser-ssh-terminal/

VPN Providers:

  1. ProtonVPN
  2. NordVPN
  3. https://www.cryptostorm.is/
  4. https://mullvad.net/en/

Hosting providers:

  1. https://www.linode.com/
  2. https://1984hosting.com/

Telegram: https://t.me/thcorg
Twitter: https://twitter.com/hackerschoice