Onion Service to secure APIs
summary
Claims that Tor and Onion Service can secure API traffic by keeping it entirely inside the Tor network, hiding metadata and removing dependence on DNS or CAs; network runs ~6–7k relays with ~300 Gbps capacity and ~150 Gbps typical usage and 2–8M daily users. Onion addresses are 56-character self-authenticating address (hash of the service public key) so impersonation is infeasible, you need no HTTPS needed or SSL certs, no port forwarding or firewall changes, demo exposes a Flask API and SSH over Tor and works though latency is higher due to three-hop routing.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:47What is Tor?
- 2:45Tor: Network
- 10:02Onion Services: Properties
- 11:49Self Authentication
- 12:51End-to-end Encryption
- 15:51Use cases
related talks
33mOnion adventures: how to use onion services and the Tor network in your web endeavors
13mPrivacy & Anonymity: Securing the Digital Economy's Most Valuable Assets
23mHow Do Tor Users Interact With Onion Services?
20mDemystifying the Darknet in 30mns or Less
54mAnonymity Loves Resilience: The Case of Tor
12mOnions Got Puzzled: On the Challenges of Mitigating Denial-of-Service...
50mCyber-crime and attacks in the dark side of the web
01h 16mAnonymity loves Diversity: The Case of Tor