No need to look far to see the impact of Lynn's presentation. Cisco last week issued a security alert and patch for a critical "heap-overflow" vulnerability in its Internetwork Operating System (IOS) that could have allowed hackers to crash or take control of the routers and switches that form the backbone of the Internet and enterprise networks. Widespread awareness of this potential exploit stems from the July Black Hat conference, where Lynn demonstrated that vulnerabilities to a certain version of IOS running in IPv6 environments could be exploited to take over--rather than simply shut down--Cisco routers and switches.
What really gets me though is that I actually sat down with Juniper at InformationWeek's offices while I was researching my story. We made the usual small talk about the mild October weather, chatted about the company's upcoming Infranet Controller appliances and Infranet Agent software, and discussed Cisco's approach to loading IOS with security features while Juniper offloads much of its perimeter security responsibilities to network appliances. If only I hadn't given up on building that time machine when I was in junior high school! Then I would have known to drop a verbal WMD on them by asking: "So, I hear you're interviewing Michael Lynn for a position at Juniper. Will he be getting a company car?" Of course, I would also have used my new powers to keep from drafting Pittsburgh's Deuce Staley as the starting running back for my fantasy football team. Alas.
Let's not lose sight of what's really important: my team might still make the playoffs and the mind of Michael Lynn will be put to good use by the only company with a legitimate shot at challenging Cisco for networking equipment supremacy. After all of the time and effort Cisco spent trying to shut down Lynn's Black Hat presentation, you couldn't have written a more compelling epilogue. But let's also give credit to Cisco. The company has responded to this summer's wakeup call and fixed the vulnerabilities in question.
The issue of vulnerability disclosure is one I expect to address in the coming months, so please weigh in with your thoughts. Please also take a minute to respond with your perspective on Juniper's hiring of Lynn. Was this a shrewd move by a vendor on its way up in the networking world, or was it a cheap shot at Cisco, given all of the time Lynn spent deconstructing and re-engineering IOS code with Cisco's blessing?