-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong wpa_supplicant configuration is generated in case of MSCHAPv2 #777
Comments
After having a look at the code, this is actually a little bit more complicated.
As you can see Not sure what the best approach to fix this would be. We definitely need to fix the interface towards |
The problem is related to an array, which is used to transform strings to the internal representation of the type: Lines 596 to 621 in e6e0039
Not sure what the best approach to fix this, would be. I can come up with something, but I'm not sure about all of the consequences. Unfortunately there seem to be no continuous integration, so I would prefer if someone with more experience with this codebase, would change the code in the best possible way. By the way: There are many more and similar definitions for key management, which are probably also not working correctly and/or rely on lenient parsing on These (among others) might be problematic: Lines 581 to 588 in e6e0039
Lines 556 to 565 in e6e0039
Lines 535 to 540 in e6e0039
Lines 513 to 519 in e6e0039
|
Fix in #780 to use the correct wpa table not the xml schema table. Further, additional change to assume mschapv2 for PEAP by default (PEAPv0) -- yast2 can set it, |
Since this has been addressed with #780, let's close this issue. |
As diagnosed in bnc#1026807, a change to wpa_supplicant in commit f24e48861d50b6b6fc5681f75d4aa75144862853 has been made, which changed the behavior in regards to
auth=
andautheap=
.The commit message reads:
The configuration files generated by wicked are affected by this, since they set
WIRELESS_EAP_AUTH='MSCHAPv2'
, which will no longer work, resulting in issues (see bug mentioned previously).The text was updated successfully, but these errors were encountered: