On Fri, Dec 19, 2008 at 11:52 AM, David Orman <[email protected]> wrote: > Hi Dan, > > Here's some more information about PEAP-GTC. > > First, a little snippit from the freeradius project: > http://wiki.freeradius.org/EAP#PEAPv1.2FEAP-GTC > It references the RFC in which PEAP-GTC is defined as an inner > authentication protocol: http://www.ietf.org/rfc/rfc3748.txt > In the RFC, the relevant section is 5.6 > > In our environment, we utilize RSA tokens with a randomly generated keys, so > I think it is likely the method you are thinking of. You're correct in your > analysis, it would certainly be an always prompt/never save bit in the > application. Running a search to gather more information to help out, all I > ran into were posts about people who had upgraded various distributions and > gotten NM 0.7.x (that had been running 0.6.x with working PEAP-GTC support), > so it does seem to be utilized somewhat frequently. wpa_supplicant appears > to still work correctly with PEAP-GTC for most people, as does NM 0.6.x, so > most people who are in the same boat as I am have been downgrading to the > older version of NM or just using wpa_supplicant directly. > > I'm happy to assist however I can in this, but I will likely be limited to > providing myself as a lab rat for testing changes. Anybody is more than > welcome to take me up on that offer. :) Let me know if there is any other > information I can gather that would help out, and thank you for looking into > this! > > Cheers, > David
I have never seen PEAP-GTC in use before but the Cisco docs I have /seem/ to use PEAPv1 and PEAP-GTC interchangeably. Have you tried setting up your connection as PEAPv1? _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
