After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 400605 - NetworkManager should support MSCHAPv2
NetworkManager should support MSCHAPv2
Status: RESOLVED DUPLICATE of bug 359369
Product: NetworkManager
Classification: Platform
Component: general
0.6.6
Other All
: Normal enhancement
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2007-01-25 13:44 UTC by Jonathan Anderson
Modified: 2007-02-09 22:07 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jonathan Anderson 2007-01-25 13:44:30 UTC
My university (and, by reading blog posts, I'm not alone) uses WPA with MSCHAPv2 for Phase 2 authentication. wpa_supplicant supports this behaviour, but there is no way to configure it with NetworkManager, so after being super-impressed with NM, I'm back to using wpa_supplicant.conf and "sudo ifup eth1". This is unfortunate, because I really like NetworkManager.

Anyway, here's my [redacted] wpa_supplicant.conf:

network={
         ssid="<ssid>"
         scan_ssid=1
         key_mgmt=WPA-EAP
         eap=PEAP
         identity="<username>"
         password="<password>"
         phase1="include_tls_length=1 peaplabel=0"
         phase2="auth=MSCHAPV2"
}

So... can NetworkManager be made to configure the phase2 field?
Comment 1 Sitsofe Wheeler 2007-02-09 18:35:47 UTC
This looks like a dup of Bug #359369 ...
Comment 2 Jonathan Anderson 2007-02-09 22:07:38 UTC
Yup, it sure is a dupe... didn't turn up when I searched the existing bugs. I was probably using "WPA" as a search term, which doesn't show up anywhere in Bug #359369.

*** This bug has been marked as a duplicate of 359369 ***