WPA2 Enterprise support (PEAP/MSCHAPv2 + EAP-TLS) #43
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sandeepmistry
commented
Dec 17, 2019
sandeepmistry
force-pushed
the
wpa2-enterprise
branch
from
ca9e945 to
70e01d2
Compare
sandeepmistry
changed the title
|
@facchinm this should be good to go now. There is one limitation, the SSID + cert + key + identity should be max ~4kB for the EAP-TLS option. However, I think that's an acceptable trade off for the first cut. |
|
LGTM! |
facchinm
approved these changes
Dec 18, 2019
This was referenced Dec 23, 2019
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This includes PR #42 and is intended to replace PR #33 .
@facchinm unfortunately I could not setup an AP to test EAP-TLS functionally.