diff --git a/servers/anonclearnetservices/0.png b/servers/anonclearnetservices/0.png new file mode 100644 index 0000000..1dd5805 Binary files /dev/null and b/servers/anonclearnetservices/0.png differ diff --git a/servers/anonclearnetservices/index.html b/servers/anonclearnetservices/index.html index d66caea..9e32872 100644 --- a/servers/anonclearnetservices/index.html +++ b/servers/anonclearnetservices/index.html @@ -62,6 +62,7 @@
In this tutorial we're going explain how you can have anonymous clearnet services, which can either remotely or self-hosted.
The main advantage here is that you have complete control over the server, if an adversary has to get his hands on the server, he has to bust down your door and find it.
The strategy here is "I use secure technology, come at me!", Which brings us to the main disadvantage however: if the technology fails you along the way for example the adversary uses a Tor 0day on you, and finds out that the hidden service is at your home IP address, then there is no way you can deny that you are the administrator of said service. In that case, using a trusted VPN that regularly deletes logs like mullvadVPN, to hide the Tor traffic, might be a lifesaver.
+There may be other attacks to figure out if you are the owner of said hidden service, like temporarily shutting down the power, or the internet connection, to see if the hidden service goes down or not.
TLDR: you have physical control over the server, but if anything goes wrong, the service is at your house. No possibility to deny that you are the administrator!