
The unfortunate part about this is that there is nothing (aside from using encrypted protocols… more on this later) we can do about this. To be clear: Tor exit nodes can see traffic as if it were just leaving your device. This includes things like usernames, passwords, session cookies, or even file uploads/downloads. FTP, HTTP, SMTP, etc.) can be seen by the exit node operator. This means that any unencrypted protocols (e.g. Tor exit nodes are the definition of a man-in-the-middle (MitM). This post will take a look at what happens when a Tor exit node operator decides to “break bad” and wreak havoc on Tor users 1.

This visibility puts quite a bit of trust in exit nodes and, for the most part, they tend to act responsibly. Since exit nodes send data to the final destination, they can see the data as if it had just left the device. Exit nodes are the final link in a Tor “circuit”, or path from the client to the server. However, you’ll notice that we haven’t dealt too much with exit nodes.

When looking at how Tor works, we’ve looked at the various types of nodes that make up the Tor network. ☰ Menu What Happens When Tor Exit Nodes Break Bad?
