From 72e9c84e56c6a0fdea0e39c22c198c9365c10ff6 Mon Sep 17 00:00:00 2001 From: midas Date: Thu, 13 Feb 2025 13:47:21 +0100 Subject: [PATCH] add link to anonymousremoteserver --- opsec/anonymous_server_monitoring/index.html | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/opsec/anonymous_server_monitoring/index.html b/opsec/anonymous_server_monitoring/index.html index 57cbde9..c025252 100644 --- a/opsec/anonymous_server_monitoring/index.html +++ b/opsec/anonymous_server_monitoring/index.html @@ -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.

- 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. +

- + First, you need to read and understand how to connect to your server safely and anonymously (see this article), grok it and then come back here. +
+
+ ... +
+ ... +
+ Done? Let's proceed. +