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

HA usecase explanation

Browse source
This commit is contained in:
urist 2024-12-19 17:32:51 +01:00
parent 38ef886296
commit e0269345a2
1 changed files with 12 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

31
opsec/high_availability/index.html
View file

@ -132,31 +132,24 @@ The adversary has identified a probable city of residence for the administrator
</div><!-- /grey -->
<!-- +++++ Second Post +++++ -->
<div id="anon1">
<div id="anon2">
<div class="container">
<div class="row">
<div class="col-lg-8 col-lg-offset-2">
<h2><b>Setup</b></h2> </br> </br>
<p></p>
<pre><code class="nim">
</code></pre>
<a href="../index.html">Previous Page</a></br></br><p><img src="../../assets/img/user.png" width="50px" height="50px"> <ba>nihilist - 00 / 00 / 00</ba></p>
<h1>SRVNAME Setup </h1>
<img src="0.png" class="imgRz">
<p>
<h2> <b>How can high availability help?</b> </h2>
In the above scenario if the onion service operator had setup a redundant, highly available server then connections would have been seamlessly sent to another server in the redundancy pool, this preventing the adversary
from extracting location information based on their operation. This works best with a server in a different country or region, making a coordinated attack by several adversaries a requirement in order to use this method for deanonymization.
<p></p>
<pre><code class="nim">
</code></pre>
<p></p>
<pre><code class="nim">
</code></pre>
</div>
</p>
</div>
</div><!-- /row -->
</div> <!-- /container -->
</div><!-- /white -->
</div><!-- /grey -->
<!-- +++++ Footer Section +++++ -->