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
27 Commits 1 Branch 23 Tags 54 MiB
Shell 75.1%
Dockerfile 9.8%
Go 5.1%
Makefile 3.8%
C 2.8%
Other 3.4%
fe656df7c3
Go to file
SkyperTHC fe656df7c3
nginx
2022-07-27 15:25:42 +01:00
config/etc nginx 2022-07-27 15:25:42 +01:00
encfs 31338 2022-07-25 13:42:33 +01:00
guest 31338 2022-07-25 13:42:33 +01:00
host 31338 2022-07-25 13:42:33 +01:00
provision 31338 2022-07-25 13:42:33 +01:00
router 31338 2022-07-25 13:42:33 +01:00
sfbin 31338 2022-07-25 13:42:33 +01:00
tor 31338 2022-07-25 13:42:33 +01:00
docker-compose.yml 31338 2022-07-25 13:42:33 +01:00
Makefile 31338 2022-07-25 13:42:33 +01:00
README.md Update README.md 2022-06-30 13:02:22 +01:00

README.md

segfault.net - back from the dead

  • THIS IS BETA TESTING ONLY *
  • JOIN US ON TELEGRAM. LET US KNOW WHAT YOU WANT AND NEED *

A root shell for every (creative) person. Free. Anonymous. Secure.

$ ssh root@beta.segfault.net # password is 'segfault'

A new instance is spawned for every new connection. Each instance has these features:

  1. Dedicated root server for every user.
  2. All traffic is routed via NordVPN.
  3. All DNS traffic is encrypted (DNS over HTTPS).
  4. TOR pre-installed.
  5. Encrypted/Persistent storage in /sec. Private to the User.
  6. Each User has his own SECRET to access his data.
  7. No trace (beside encrypted data) after the User logs off.
  8. No logs are kept.

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

Cluster can be deployed in various regions for less latency. Misc infos:

  1. https://docs.docker.com/engine/security/userns-remap/
  2. On small deployments the OpenVPN Server can be the same as Server[12]. This allows to run everything off 1 single server.
  3. AWS Fargate could be utilized by nesting the entire setup in a Docker-in-Docker (dind) configuration.

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