https://bugzilla.novell.com/show_bug.cgi?id=396347 User jsnel@few.vu.nl added comment https://bugzilla.novell.com/show_bug.cgi?id=396347#c14 Joris Snellenburg <jsnel@few.vu.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|jsnel@few.vu.nl | --- Comment #14 from Joris Snellenburg <jsnel@few.vu.nl> 2008-06-19 02:55:02 MDT --- (In reply to comment #11 from Helmut Schaa)
Could you please try if creating a new connection works fine? Editing connections is still not that well tested.
Making a new connection does in fact work, I am now connected to a WPA/WPA2 TKIP/AES EAP-TTLS network using the PAP authentication protocol. Although the edit connection feature doesn't seem to retrieve all the settings (i.e. my TTLS setting and Phase2 setting) it does seem to save this information when I enter it and click Connect&Save or Save in it's configuration files so it does work. Next thing on the list is test it with certificates (CA and radius). With a program for Windows called SecureW2 these certificates can be retrieved from the network automatically, is there also a possibility for this with KNetworkManager or any other program? Also about EAP/GTC, from Wikipedia: ============================== PEAPv1/EAP-GTC was created by Cisco as an alternative to PEAPv0/EAP-MSCHAPv2. It allows the use of an inner authentication protocol other than Microsoft's MSCHAPv2. EAP-GTC (Generic Token Card) is defined in RFC 3748. It carries a text challenge from the authentication server, and a reply which is assumed to be generated by a security token. EAP-GTC does not protect the authentication data in any way. Even though Microsoft (along with RSA and Cisco) co-invented the PEAP standard, Microsoft never added support for PEAPv1 in general, which means PEAPv1/EAP-GTC has no native Windows OS support. Since Cisco has always favored the use of its own less secure proprietary LEAP and EAP-FAST protocols over PEAP and markets them as simpler certificate-less solutions, standardized PEAP is rarely promoted by Cisco. With no interest from Microsoft to support PEAPv1 and little interest from Cisco to promote PEAP in general, PEAPv1 authentication is rarely used. There is no native OS support for this EAP protocol. Although there is no in-built support for PEAP-GTC in MS Windows, it is supported by the Cisco CCX extensions program. CCX compatibility is enabled by default on many vendor-provided 802.11A/B/G clients. This version of PEAP is defined through the IETF internet draft "draft-josefsson-pppext-eap-tls-eap-10". Note that this is an individual submission and not standardized in the IETF. Note that Cisco's implementation of PEAPv1 also supports EAP-SIM as the inner EAP method, other than EAP-GTC. ============================== -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.