The post Worth Reading: One old guy’s advice appeared first on 'net work.
The post Worth Reading: IPv6 performance (again) appeared first on 'net work.
While Greg was at the IETF in Berlin, Sue Hares and I—the two current co-chairs of the I2RS working group—had a general discussion around what the big idea is and where the working group is headed. You can listen to the recording at Packet Pushers.
The post On the ‘net: I2RS on Packet Pushers appeared first on 'net work.
For the last couple of days I’ve been messing with Cisco’s VIRL on Packet’s bare metal service. I don’t do enough labbing now to spend multiple thousands of dollars building a lab in my house, and I want something that I can use from anywhere without opening a lot of holes in my home network when I’m on the road, so the Packet service seems like something useful to get running.
Forthwith, some observations and hints for those who might be thinking about doing this. Some of this might be obvious to other folks, I know, but—maybe me writing them down here will be somehow helpful, and save other folks some time.
An observation—this all feels a little (okay, maybe a lot) clunky’ish. There’s a lot of steps, it takes a long time to set up, etc. There are a lot of moving parts, and they interconnect in interesting ways. Maybe this will all get better over time, but for now, if you’re going to do this, plan on spending at least a half a day, probably more, just getting all the pieces to work.
Some places I ran into trouble, and things I needed to configure that I had Continue reading
The post Worth Reading: Photographing the Internet appeared first on 'net work.
How many times have you heard this? Or this?
Two of the most oft repeated, and driven home, ideas in modern times are be true to yourself and do what you love. But just because they’re oft repeated and driven home doesn’t mean they are actually true. The problem with both statements is they have just enough truth to sound really plausible—and yet they are both simplistic enough to be dangerous when taken raw.
Or maybe it’s just that I’m a grumpy old man who’s been in a bad mood for the last couple of weeks, and misery likes company.
Let’s try to put some reality into the do what you love statement.
Sometimes you’re just not very good at what you love to do. When I was a kid, I wanted to be an artist. And then a musician. Apparently there are no real jobs for artists or musicians with my somewhat mediocre skills in these two areas. I just have to face it—I’m never going to be a professional basketball player, either. Sometimes it doesn’t matter how much you love something, you just don’t have the skills to master it.
Sometimes there’s just no market for what you Continue reading
We introduce Flip Feng Shui (FFS), a new exploitation vector which allows an attacker to induce bit flips overarbitrary physical memory in a fully controlled way. FFS relies on hardware bugs to induce bit flips over memoryand on the ability to surgically control the physical memory layout to corrupt attacker-targeted data anywhere inthe software stack. We show FFS is possible today with very few constraints on the target data, by implementingan instance using the Rowhammer bug and memory deduplication (an OS feature widely deployed in production).Memory deduplication allows an attacker to reverse-map any physical page into a virtual page she owns as long as the page’s contents are known. Rowhammer, in turn, allows an attacker to flip bits in controlled (initially unknown) locations in the target page. -(PDF) Usenix via Schneier on Security
The post Worth Reading: A new bit flipping attack appeared first on 'net work.
The post Worth Reading: Big data is making us more more boring appeared first on 'net work.
In the last post in this series, I discussed using SR labels to direct traffic from one flow onto, and from other flows off of, a particular path through a DC fabric. Throughout this series, though, I’ve been using node (or prefix) SIDs to direct the traffic. There is another kind of SID in SR that needs to be considered—the adj-sid. Let’s consider the same fabric used throughout this series—
So far, I’ve been describing the green marked path using the node or (loopback) prefix-sids: [A,F,G,D,E].
What’s interesting is I could describe the same path using adj-sids: [a->f,f->g,g->d,d->e],
where the vector in each hop is described by a single entry on the SR stack. There is, in fact, no difference between the two ways of describing this path, as there is only one link between each pair of routers in the path. This means everything discussed in this series so far could be accomplished with either a set of adj SIDs ore a set of node (prefix) SIDs.
Given this, why are both types of SIDs defined? Assume we zoom in a little on the border leaf node in this topology, and find—
Assume—
The post Worth Reading: What Sauron Tells Us appeared first on 'net work.
The post Worth Reading: Lawless government hacking appeared first on 'net work.
The post Worth Reading: Hosts versus the network appeared first on 'net work.
The post Worth Reading: Reopening the going dark debate appeared first on 'net work.
A lot of people seem to be looking forward to the day we build a network without an operator; to wit—
I hope not, because machines are more brittle than humans. Totally automated security fails much more often than security that uses a blend of people and algorithms. Machines do well at repetitive tasks, humans at catching the things that don’t fit into the algorithm’s state machine. Taking the person out of the network just means there’s no-one there to see when the state machine fails.
And it will fail—at some point. I know we like to believe that machines break less often, but I’m pretty certain there’s a counterpoint to this: when machines break, it’s more likely to be catastrophic. I’m not convinced replacing people with algorithms always reduces damage so much as move the potential damage around.
I hope not, because machines separate the decision from the decision maker. Continue reading
The post Worth Reading: Container defense in depth appeared first on 'net work.
The post Worth Reading: Your chance to say no appeared first on 'net work.
There are some days I wish I could travel back in time and “fix” the time I wasted through an hour, a day, or a week working on something that really wasn’t worth my time, or just wandering through links on the Internet, looking at things I don’t really (ultimately) care about. My time management skills are, honestly, often lacking. There doesn’t seem to be a way, does there, though?
Or maybe there is. Let’s twist our brains a little and think about it this way. Tomorrow is going to be the day we wish we could travel into from the day after tomorrow to fix, right? So what if we did reverse time travel and fix tomorrow today? Sure, sounds nice, but how? The answer might seem a little trivial, but it’s only apparently trivial, rather than trivial in real life.
Once answer is the humble todo list. I know, you’ve made one of these before—in fact, you probably already have one, don’t you? And it’s never really helped, right? Well, let’s see if we can figure out how to supercharge to make it a bit more effective. To begin, we have to try to understand how a todo Continue reading
The post Worth Reading: Tracking the hackers appeared first on 'net work.
The post Worth Reading: Network monitoring appeared first on 'net work.