Enable MSCHAPv2 with StrongSwan. #30642
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
StrongSwan on Void currently has issues with EAP-MSCHAPv2 in different ways.
(1) eap-identity needs to be enabled in order for config files with
eap_identity=%any
and similar lines to work (you essentially end up withEAP_NAK
whenEAP_IDENTITY
is requested);(2) eap-mschapv2 requires
md4
to be enabled as a plugin(3) eap-dynamic might be required on some setups, so this pull request enables it to avoid issues in the future.
General
Have the results of the proposed changes been tested?
Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
I have not tested if it runs on any of the cross builds, I simply tested that it indeed does build.