How TOR Works- Computerphile

When guys like these become professors, they end up making a generation of youngsters who revolutionise the technology.

Could you also talk about garlic routing? Which is more vulnerable to leeks?

As someone currently going for their masters in cybersecurity. They have been a massive help in understanding comp sci and IT concepts. While my professors are great people and they mean the best its was easier for me to get a concept down with a 10-30min computerphile video than a 4 hour long lecture with no practical application. Just wanted to say thanks chaps you been a massive help.

"No one really knows anything about what's going on at all." Great description of my life.

I wish he was my teacher when I first took up computer science.

Confidentiality is hiding the message, anonymity is hiding the sender.

Using Tor to access Facebook... Oh what irony...

Traffic Analysis (discussed from about 11:20 to 13:00) is one of the major reasons tor works best when a lot of people near you are also connecting to the network. The more people that are connected to the same node, the "noisier" it is on the harder it is to correlate the inputs and outputs. Of course, this resistance to analysis is at a cost: all of that extra traffic also has to be processed by the node at some point, making it slower, so it's a bit of a balancing act

That preview picture tho. At first blink I was sure that was anything but an onion lol

The absolute best explanation of onion routing ever heard.

When someone else goes "TOR router" and you're there like "The Onion Router router?"

This is definitely my favorite guy on this channel.

I love that people are always trying to charge money for computer courses and that, whereas the best teachers on youtube do it for free. I have so much respect for Mike and Tom. Keep doing what you are a doing and set up a Patreon because the information you are teaching on this channel is amazing and I would gladly donate what I can to you guys.

A key point left out: Network requests can often have blatant identifiers of who sent that request, and the specifics about what they're doing. It's not just always seemingly arbitrary requests that give no hint of who issued the request. Like when using any sort of system you have to user a user ID or password for. This means the final node on the routing path actually can figure out info about who originated the request, and possibly why, despite having the multiple levels of encryption and routing between themselves and the originator

Clearest description of Tor I've ever heard, obviously a teacher!

I love Dr. Pound's in-depth explanations, and this channel, too.

4:06 Layer encryption. 6:02 Attack. 7:42 Onion routing. 8:08 Speed. 9:24 Eavesdropping. 10:28 Drawbacks. 13:03 Cells.

Been following for years and I love the content. Always so fascinating. One of the best channels on YT.

Great insight for a newcomer to the topic, thank you for taking the time to explain!

Discovering this channel with this nice topic : thanks a lot! Short question, Mike Pound evokes the weakness of finding timely correlations between entry and exit points. But, could some kind of controlled shuffling of the various requests do the trick ( a mixing with other requests)?