oxeo0/blog-contributions
1
0
Fork 0
mirror of http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/blog-contributions.git synced 2025-07-02 11:56:40 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fixed typos and broken link

Browse source
This commit is contained in:
Zesc 2024-08-24 16:01:33 +02:00
parent 6eb68f0270
commit dcf265743e
38 changed files with 88 additions and 88 deletions
Download patch file Download diff file Expand all files Collapse all files

2
opsec/endgame/index.html
View file

@ -63,7 +63,7 @@
<a href="../index.html">Previous Page</a></br></br><p><img src="../../assets/img/user.png" width="50px" height="50px"> <ba>nihilist@mainpc - 2024-04-13</ba></p>
<h1>EndGame V3 Setup </h1>
<img src="0.png" class="imgRz">
<p>In this tutorial we're going to setup the EndGameV3 Anti DDOS / Load Balancer / WAF service popularized by Dread, it was originally built to block off the incessant <a href="https://blog.torproject.org/tor-network-ddos-attack/">DDOS attacks</a> that onion services were facing. Because of that, EndGame was developped, along with the <a href="https://blog.torproject.org/introducing-proof-of-work-defense-for-onion-services/">Proof of Work (POW) Defense released by TorProject</a> for more details you can click <a href="https://community.torproject.org/onion-services/ecosystem/technology/pow/">here</a>. </p>
<p>In this tutorial we're going to setup the EndGameV3 Anti DDOS / Load Balancer / WAF service popularized by Dread, it was originally built to block off the incessant <a href="https://blog.torproject.org/tor-network-ddos-attack/">DDOS attacks</a> that onion services were facing. Because of that, EndGame was developed, along with the <a href="https://blog.torproject.org/introducing-proof-of-work-defense-for-onion-services/">Proof of Work (POW) Defense released by TorProject</a> for more details you can click <a href="https://community.torproject.org/onion-services/ecosystem/technology/pow/">here</a>. </p>
<pre><code class="nim">
Endgame should be on a separate server to your backend server. It only proxies content from your backend to the user. You will still need to configure your backend to handle requests from the Endgame Front.