mirror of
http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/opsec-blogposts.git
synced 2025-06-08 07:29:31 +00:00
fix stuff
This commit is contained in:
parent
7739e73322
commit
9a415258f4
84 changed files with 313 additions and 191 deletions
|
@ -25,6 +25,8 @@ Out of those requirements, we have 2 possibilities as to where you can run a sen
|
|||
|
||||
## **Self Hosting : Full Physical Control but Risky!**
|
||||
|
||||

|
||||
|
||||
 **Pros:**
|
||||
|
||||
Everyone has an internet connection, and if you live in a country that does not actively sensor the tor network, it can be interesting to host your own physical server which runs your hidden .onion service
|
||||
|
@ -43,6 +45,8 @@ If the adversary has the ability to crack open the security of the technology us
|
|||
|
||||
## **Remote Hosting: No Physical Control but Safer!**
|
||||
|
||||

|
||||
|
||||
 **Cons:**
|
||||
|
||||
Since the Idea here is to run the sensitive service (and most of the time, it's not allowed by the cloud provider), **If there is no redundancy / high availability, The longevity of the service would depend on how long the service remains unnoticed by the cloud provider.**
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue