How TOR Works- Computerphile

1,738,481
0
2017-05-31に共有
What goes on TOR stays on TOR, or so we hope. Dr Mike Pound takes us through how Onion Routing works.

This video was formerly called "Onion Routing"

EXTRA BITS:    • EXTRA BITS: Onion Routing - Computerp...  
End to End Encryption:    • End to End Encryption (E2EE) - Comput...  
Deep Web / Dark Web:    • Secrets of the Deep Dark Web (Deep Da...  

www.facebook.com/computerphile
twitter.com/computer_phile

This video was filmed and edited by Sean Riley.

Computer Science at the University of Nottingham: bit.ly/nottscomputer

Computerphile is a sister project to Brady Haran's Numberphile. More at www.bradyharan.com/

コメント (21)
  • When guys like these become professors, they end up making a generation of youngsters who revolutionise the technology.
  • 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.
  • Could you also talk about garlic routing? Which is more vulnerable to leeks?
  • 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
  • "No one really knows anything about what's going on at all." Great description of my life.
  • @Beateau
    Confidentiality is hiding the message, anonymity is hiding the sender.
  • @ghnna
    When someone else goes "TOR router" and you're there like "The Onion Router router?"
  • That preview picture tho. At first blink I was sure that was anything but an onion lol
  • 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
  • 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.
  • Been following for years and I love the content. Always so fascinating. One of the best channels on YT.
  • I love Dr. Pound's in-depth explanations, and this channel, too.
  • Clearest description of Tor I've ever heard, obviously a teacher!
  • few questions: 1- why not asymmetric encryption as opposed to symmetric? 2- could you make it harder to de-anomynise you if packets had a short, random delay before being sent to the next node? 3- could you make it harder to de-anomynise you if you added dummy data or dummy packets at the entry and/or exit points?
  • Great insight for a newcomer to the topic, thank you for taking the time to explain!
  • I love the Computerphile episodes that Mike pound is in!