Firewalls and Defence in Depth: Why One Wall Is Never EnoughEvery post in this series has had a shadow. The OSI layers trusting the layer beneath. IP addresses that locate a machine but authenticate no one. DNS that cannot verify its own answers. TCP handshake5d ago · 15 min readvictor-chukwuemeka.hashnode.dev
Routing and BGP: How the Whole Internet Agrees Where to Send Your DataWe have come a long way. We have addresses, names that resolve to them, reliable connections, and encryption that protects what those connections carry. But every single one of those posts rested on aAug 30 · 18 min readvictor-chukwuemeka.hashnode.dev
TLS and Certificates: How Two Strangers Agree on a Secret, and Why Your Browser Trusts AnyoneLast post ended with a promise. We had explained that HTTPS is ordinary HTTP running inside an encrypted tunnel called TLS, Transport Layer Security, and that this tunnel provides confidentiality, intAug 14 · 18 min readvictor-chukwuemeka.hashnode.dev
HTTP and HTTPS: The Language of the Web, and the S That Protects ItWe have climbed a long way up the stack. We gave data a network to travel on, a way to travel in packets, an address to aim for, a name that resolves to that address, and in the last post, a reliable Aug 8 · 18 min readvictor-chukwuemeka.hashnode.dev
TCP vs UDP: Reliability or Speed, the Choice Every Connection MakesWe have spent this series following data on its journey. We gave it a network to travel on, a way to travel in packets, layers to pass through, an address to aim for, and a name that resolves to that Aug 2 · 17 min readvictor-chukwuemeka.hashnode.dev
