-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[BUG] ConnectWiFiNetworkAsync doesn't support WPA3 (SAE) #23402
Comments
afeatherstone-mm
added a commit
to afeatherstone-mm/connectedhomeip
that referenced
this issue
Oct 31, 2022
wpa_supplicant will use SAE, if required by the network. Support for WPA3 is required as part of v1.0 of the Matter Specification (refer to 11.8.8.4 for details). Resolves project-chip#23402.
afeatherstone-mm
added a commit
to afeatherstone-mm/connectedhomeip
that referenced
this issue
Nov 1, 2022
wpa_supplicant will use SAE, if required by the network. Support for WPA3 is required as part of v1.0 of the Matter Specification (refer to 11.8.8.4 for details). Resolves project-chip#23402.
afeatherstone-mm
added a commit
to afeatherstone-mm/connectedhomeip
that referenced
this issue
Nov 1, 2022
wpa_supplicant will use SAE, if required by the network. Support for WPA3 is required as part of v1.0 of the Matter Specification (refer to 11.8.8.4 for details). Resolves project-chip#23402.
afeatherstone-mm
added a commit
to afeatherstone-mm/connectedhomeip
that referenced
this issue
Nov 2, 2022
wpa_supplicant will use SAE, if required by the network. Support for WPA3 is required as part of v1.0 of the Matter Specification (refer to 11.8.8.4 for details). Resolves project-chip#23402.
afeatherstone-mm
added a commit
to afeatherstone-mm/connectedhomeip
that referenced
this issue
Nov 2, 2022
wpa_supplicant will use SAE, if required by the network. Support for WPA3 is required as part of v1.0 of the Matter Specification (refer to 11.8.8.4 for details). Resolves project-chip#23402.
afeatherstone-mm
added a commit
to afeatherstone-mm/connectedhomeip
that referenced
this issue
Nov 3, 2022
wpa_supplicant will use SAE, if required by the network. Support for WPA3 is required as part of v1.0 of the Matter Specification (refer to 11.8.8.4 for details). Resolves project-chip#23402.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
This stale issue has been automatically closed. Thank you for your contributions. |
mergify bot
pushed a commit
that referenced
this issue
Nov 17, 2023
wpa_supplicant will use SAE, if required by the network. Support for WPA3 is required as part of v1.0 of the Matter Specification (refer to 11.8.8.4 for details). Resolves #23402. Co-authored-by: Andrei Litvin <andy314@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reproduction steps
From the definition of the AddOrUpdateWiFiNetwork Command in section 11.8.8.4 of [1]
In the handling of the ConnectNetwork Command in ConnectWiFiNetworkAsync, the
key_mgmt
is hardcoded toWPA-PSK
For networks that only support SAE, this results in the DUT failing to authenticate to the network.
[1] Matter Specification Version 1.0, document 22-22349-001_Matter-1.0-Core-Specification.pdf
Bug prevalence
Whenever I do this
GitHub hash of the SDK that was being used
v1.0
Platform
raspi
Platform Version(s)
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: