The post Worth Reading: Said no CEO, ever appeared first on 'net work.
The post Worth Reading: Multiple DNS providers and DDoS appeared first on 'net work.
The post Worth Reading: Insurance companies and free stuff appeared first on 'net work.
The post Worth Reading: Engineering infrastructure at scale appeared first on 'net work.
The post Worth Reading: Using rowhammer to root Android appeared first on 'net work.
The post Worth Reading: Energy Efficiency and Data Centers appeared first on 'net work.
The post Worth Reading: Dyn’s DDoS Reveals IoT Weak Points appeared first on 'net work.
Just in time for Hallo’ween, the lucky thirteenth post in the BGP code dive series. In this series, we’re working through the Snaproute Go implementation of BGP just to see how a production, open source BGP implementation really works. Along the way, we’re learning something about how larger, more complex projects are structured, and also something about the Go programming language. The entire series can be found on the series page.
In the last post in this series, we left off with our newly established peer just sitting there sending and receiving keepalives. But BGP peers are not designed just to exchange random traffic, they’re actually designed to exchange reachability and topology information about the network. BGP carries routing information in updated, which are actually complicated containers for a lot of different kinds of reachability information. In BGP, a reachable destination is called an NLRI, or Network Layer Reachability Information. Starting with this code dive, we’re going to look at how the snaproute BGP implementation processes updates, sorting out NLRIs, etc.
When you’re reading through code, whether looking for a better understanding of an implementation, a better understanding of a protocol, or even to figure out “what went wrong” on Continue reading
The post Worth Reading: The Internet Needs a Security Upgrade appeared first on 'net work.
The post Worth Reading: The Facebook Wedge 100 appeared first on 'net work.
Ethan pointed me to this post about complexity and incremental improvement in a slack message. There are some interesting things here, leading me in a number of different directions, that might be worth your reading time. The post begins with an explanation of what the author calls “Keith’s law”—
The author attributes this to the property of emergence; given I don’t believe in blind emergence, I would attribute this effect to the combined intertwining of many intelligent actors producing an effect that at least many of them probably wanted (the improvement of the complex system), and each of them working in their own spheres to achieve that result without realizing the overall multiplier effect of their individual actions. If that was too long and complicated, perhaps this is shorter and better—
The law of Continue reading
The post Worth Reading: IoT devices and DDoS attacks appeared first on 'net work.
The post Worth Reading: The need for loud cyber weapons appeared first on 'net work.