Provided by Dread and White House Market. With help from Big Blue Market and Empire Market.
EndGame is
- a front system designed to protect the core application servers on an onion service in a safe and private way.
- locally complied and locally run (no trusted or middle party).
- a combination of multiple different technologies working together in harmony (listed below).
- FREE FOR ALL TO USE!
- arguably magic ㄟ( ▔, ▔ )ㄏ
- Fully scripted and easily deploy-able (for mass scaling!) on blank Debian 10 systems.
- Full featured NGINX LUA script to filter packets and provide a captcha directly using the NGINX layer.
- Rate limiting via Tor's V3 onion service circuit ID system with secondary rate limiting based on a testcookie like system.
- Easy Configuration for both local and remote (over Tor) front systems.
- Easily configurable and change-able to meet an onion service's needs.
It can also:
- Cause you to grow a bigger dick than the asshole DDOSER (true figurally, lies probably)
- Save you millions of dollars do to DDOSER's downing your site for ransom or for their extorting fees.
- Make it look like you know what the fuck you are doing.
Endgame uses a number of open source projects (and libraries) to work properly.
Projects:
- NGINX - NGINX! A web server obviously to provide the packet handling, threading, and proxying.
- Tor - Tor is free and open-source software for enabling anonymous communication. It's awesome and makes all this possible.
- Vanguards - A safer onion service circuit building system (to prevent some traffic analysis attacks)
- STEM - A python controller for Tor.
- NYX - A command-line monitor for Tor (to easily check the endgame front's Tor process.
- V3 OnionBalance - A distributed DNS round-robin like system on Tor to allow load-balancing and elimiate single points of failure.
- OpenSSL - A dependency for a lot of this projects and libraries.
- Python3 - A easy to work with programming language we use for background image generation.
NGINX Modules:
- Socks NGINX - A NGINX module to allow proxying to Tor onion services directly on the NGINX layer.
- NAXSI - A high performance web application firewall for NGINX.
- Headers More - A module for better control of headers in NGINX.
- Echo NGINX - A NGINX module which allows shell style commands in the NGINX configuration file.
- LUA NGINX - The power of LUA into NGINX via a module. This allows all the scripting, packet filtering, and captcha functionality EndGame does.
- NGINX Development Kit - Development Kit for NGINX (dependency)
Libraries:
- LUAJIT2 NGINX - Just in time compiler for LUA.
- LUA Resty String - String functions for ngx_lua and LUAJIT2
- LUA Resty Cookie - Provides cookie manipulation
- LUA Resty Session - Provides session manipulation
- LUA Resty AES - AES Functions file for LUA. Used for shared session cookies.
- LUA GD - GD image generation bindings For LUA
EndGame requires configuration to work properly.
The main configuration can be found at the top of the setup.sh file. It customizes most of the script
There are options. Such as:
- MASTERONION - Your V3 Master OnionBalance Address WITHOUT http:// (example: dreadytofatroptsdj6io7l3xptbet6onoyno2yv7jicoxknyazubrad.onion)
- TORAUTHPASSWORD - Password which is used for your Tor Control Port Authentication with NGINX. Alphanumeric without spaces (example: passwordIcanremembertyping)
- KEY - Alphanumeric Key for the shared front session key. Random between 64-128 would do fine. (example: isthis64charactorsalreadyicantbelieveitwowsocoolwaitnotyetohdarn)
- SALT - 8 character salt used with the key. 8 random alphanumeric characters (example: saltsalt)
- HEXCOLOR - HEX color put into the css file to be not purple but your main site's color. Any CSS hex will work. (example: #9b59b6)
There is also some editing you need to do in the caphtml_d.lua, naxsi_whitelist.rules, site.conf, and torrc files.
resty/caphtml_d.lua- Two Base64 Images. The favicon (line 143) and main logo (line 162). You can use this for the favicon and this for the main logo.naxsi_whitelist.rules- NAXSI's Whitelist Rules with some internal rules see this. To be configured for your specific application's use case.site.conf- Line 110 and 111 has the two rate limiting EndGame does. One by the circuit ID and one by the cookie. Depending on how your site calls files you may need to change these values.- Defaulty set to 3 consistent on line 110 and 111. 110 for circuit. 111 for cookie.
- Line 245 has a nodelay burst of 6 for the circuit. Line 251 has a nodelay burst of 6 for the cookie.
- Line 268-272 socks proxy_pass system. If you want EndGame to pass the filtered request over Tor you uncomment the socks_* lines and change the exampleprivatev3onion.onion to your core webserver's private v3 address.
- Line 273 regular proxy_pass. If you have a secure local connection you want to use the regular proxy_pass for reliability and latency improvements. Just change it to your core webserver's private IP.
torrc- Depending on what you set your burst as change the HiddenServiceMaxStreams value to that plus 2.
EndGame is HIGHLY scripted. Which means it is important you run it on the system that it is intended for or there could be issues. Endgame is designed for DEBIAN 10.
You need a v3 onionbalance master onion! There is a script included in the onionbalance folder. Onionbalance signed specific descriptors and publishes them to the Tor network. There is no site traffic that goes through onionbalance. As such you can put it on a low powered server or even on your core server. Recommendation is 2 CPU Cores with 2GB of RAM.
After you get your onionbalance master onion you should configure the endgame script for your site with the correct variables. While EndGame is designed to work for most onion services it isn't perfect for everyone. You will need to customize it for your own needs.
Transfer the files over to a blank debian 10 system with ideally 4 CPU cores and 4GB of RAM. High clocked cores are important (at least 3GHZ). Tor is single threaded with minimal hardware acceleration; getting higher performance cores will provide more resistance to attacks.
After the files are transferred make the setup.sh file executable and run it with bash. It will do the full setup process and export an onion URL. Visit that onion and hopefully everything will work. If not look at the error logs (located in /var/logs/nginx/) and see where you messed up.
Scale out. Without scaling out you are bring a knife to a gun fight. At minimum you need 3 fronts. Onionbalance v3 doesn't have distinct descriptors which means if you go past about 6-9 fronts there might be some descriptor sizing issues on the default onionbalance setup. Endgame does make it much harder to take you down but you need to scale to keep up. Otherwise your front's Tor will get overloaded and you will go down. It's a dick measuring contest between you and the attacker. By scaling out you are effectively adding more length to your dick.
After scaling out with multiple fronts add all their onion addresses to onionbalance's configuration and run it. Now you can publish that onionbalance master address as an EndGame protected address. That is it. Repeat these steps as many times as needed to make as many Endgame protected addresses to outscale any DDOSER.
EndGame isn't perfect. It can't protect against introduction cell type attacks (the Tor project will need to add POW at the introduction points to fix that). But it does provide good protection and scaling which makes it much harder to take you down overall for whatever people throw at you.
This all is a major step forward for the darknet community. Never give in to the extorting DDOSERS. You are only paying to be attacked with more power in the future. Instead stand together and say "NO". As a united front we will reach heights never seen before.