FS#51750 - [wpa_supplicant] 1-2.6-2 fails with MSCHAPV2

Attached to Project: Arch Linux
Opened by Carl Mueller (cmlr) - Tuesday, 08 November 2016, 21:08 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 14 November 2016, 15:02 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: The testing version of wpa_supplicant 1-2.6-2 fails with MSCHAPV2. The previous version, wpa_supplicant version 1:2.6-1, worked for me. (It took me some time to learn that one should use "MSCHAPV2", not "MSCHAPv2" in version 1:2.6-1).


Additional info:
* package version(s) 1-2.6-2
* config and/or log files etc. I've attached my netctl configuration file for the connection.


Steps to reproduce: Try to connect to a server requiring MSCHAPV2. For example, such connections are usually required on the eduroam network.
   ur_connected (0.3 KiB)
This task depends upon

Closed by  Doug Newgard (Scimmia)
Monday, 14 November 2016, 15:02 GMT
Reason for closing:  None
Comment by Mantas Mikulėnas (grawity) - Saturday, 12 November 2016, 11:09 GMT
Could not reproduce with 3 networks. Please post actual error messages, or a full debug log from `wpa_supplicant -d -d -d -i wlan0 -c /tmp/ur_connected.conf`.

Also note that older versions *didn't* actually accept anything but 'MSCHAPV2' either – they merely *ignored* unknown phase2 values and accepted anything the server offers, while still printing [TLS: Unsupported Phase2 EAP method 'MSCHAPv2'] in debug mode. (Tested with 2.5, 2.4, and 2.3.)
Comment by Carl Mueller (cmlr) - Monday, 14 November 2016, 13:34 GMT
Strange, wpa_supplicant worked. The problem must be with my netctl configuration. So I guess you can close this bug report.

Loading...