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

add link to anonymousremoteserver

Browse source
This commit is contained in:
midas 2025-02-13 13:47:21 +01:00
parent 0e3d225f94
commit 72e9c84e56
1 changed files with 11 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

16
opsec/anonymous_server_monitoring/index.html
View file

@ -170,12 +170,18 @@
Whenever you connect to your server, such as for monitoring or other administrative tasks, if you do so through the clearweb then you are liable to being recorded. Even when using SSH you will leave a trail of metadata all the way back to your access point. That might be enough to get your door busted down the line.
<br><br>
In the following part of the post we will look into:
In the following part of the post we will look into how to set up advanced monitoring tools so you don't have to keep an eye on a bunch of tmux sessions with glances/top open in order to know the behaviour of your systems over time.
<br><br>
<ul>
<li>How to connect to your server safely and anonymously (see <a href="http://blog.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/opsec/anonymousremoteserver/index.html">this article</a>) </li>
<li>How to set up advanced monitoring tools so you don't have to keep an eye on a bunch of tmux sessions with glances/top open</li>
</ul>
First, you need to read and understand how to connect to your server safely and anonymously (see <a href="/opsec/anonymousremoteserver/index.html">this article</a>), grok it and then come back here.
<br>
<br>
...
<br>
...
<br>
Done? Let's proceed.
<br>
</div>
</div><!-- /row -->