X

Time for an open-source 802.1x supplicant

Jon Oltsik
Jon Oltsik is a senior analyst at the Enterprise Strategy Group. He is not an employee of CNET.
Jon Oltsik
2 min read

In the security and wireless networking world, 802.1x is a big deal. This is the Layer 2 protocol that enables device authentication. The protocol helps keep war drivers off wireless networks and is also a foundational technology for client security initiatives like Cisco NAC, Microsoft NAP and the Trusted Computing Group's TNC.

No doubt, 802.1x is a step in the right direction, but now that Cisco is acquiring Meetinghouse, there is a problem. The 802.1x protocol depends upon client code called a supplicant. Cisco and Microsoft have been dabbling in the 802.1x supplicant and authentication protocol business for a while but there were always a few savvy independents to offer a more pedestrian alternative. First there was Funk, but it was gobbled up by Juniper in 2005. This move pushed all the independent networking vendors to do business with Meetinghouse but alas, now it too is part of a bigger whole.

This leaves the remaining networking bunch like Enterasys, Extreme, F5, Foundry, HP and Nortel in a bit of a bind. They need 802.1x supplicants but don't want to pad the pockets (or the initiatives) of Cisco, Juniper and Microsoft.

I have a suggestion for these guys: open source. There are some really smart guys at the University of Utah who have developed an open-source 802.1x supplicant but they need partners to help them move the ball forward. What's needed is an open-source 802.1x supplicant that emulates the success of the Firefox browser--i.e. a downloadable client that is easy to configure and install--and always works.

It's there for the taking and the time is right. Now which networking vendor will show its leadership and brains?