oxeo0/opsec-blogposts
1
0
Fork 0
mirror of http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/opsec-blogposts.git synced 2025-06-08 05:19:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

fixes for truecrypto

Browse source
This commit is contained in:
oxeo0 2025-05-26 19:48:03 +02:00
parent 0195d81d40
commit 90f6d14be9
14 changed files with 9 additions and 98 deletions
Download patch file Download diff file Expand all files Collapse all files

2
anonymityexplained/index.md
View file

@ -175,7 +175,7 @@ In the left image, although there are 4 groups, everyone person inside of a grou
However, in the right image, the groups are transparent and people are distinct. You can see the people in each overlapping and, with the combined information that you are part of all four groups, they can easily deanonymize you in the very small overlapping.
So, by using tools ([TOR](../torvsvpns/index.md) , [XMR](../finances/index.md), etc) where every user is identical and non-identifiable, we are not only minimizing bit leakage but also **making most leaked bits unusable** , significantly decreasing deanonymization risk.
So, by using tools ([TOR](../torvsvpns/index.md) , [XMR](../truecrypto/index.md), etc) where every user is identical and non-identifiable, we are not only minimizing bit leakage but also **making most leaked bits unusable** , significantly decreasing deanonymization risk.
It's recommended to be of roughly aware of how many bits you have leaked in an anonymous persona in order to maintain anonymity. We can take advantage of bit leakage by providing **false information which may mislead an adversary.**