[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #28921 [Core Tor/Stem]: tor-prompt command 'GETINFO desc/all-recent > /dev/null' fails
#28921: tor-prompt command 'GETINFO desc/all-recent > /dev/null' fails
---------------------------+-----------------------------------
Reporter: wagon | Owner: atagar
Type: defect | Status: needs_information
Priority: Medium | Milestone:
Component: Core Tor/Stem | Version:
Severity: Normal | Resolution:
Keywords: descriptor | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
---------------------------+-----------------------------------
Comment (by atagar):
> This is the node which knows IP of Tor user. If guard is known it is
very simple to deanonymize tor user.
This is incorrect. Eavesdropping on a guard simply tells you that someone
is using tor. Not where they're going. Deanonymization, say via a
correlation attack, requires monitoring both your entry *and* exit
traffic.
The strength of tor is this distribution of information. It's easy (albeit
malicious and in many places illegal) to snoop on who uses tor by running
a guard. It's also easy to figure out what tor is being used for by
snooping on an exit. What tor makes difficult is **deanonymizing** you
which requires both at the same time, which thanks to the size of the tor
network is quite difficult.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28921#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs