summaryrefslogtreecommitdiff
path: root/rs/java/android/renderscript/ProgramFragment.java
diff options
context:
space:
mode:
authorXin Deng <deng@codeaurora.org>2019-11-08 15:27:33 +0800
committerXin Deng <deng@codeaurora.org>2019-11-15 17:21:29 +0800
commit0a9e31ae63c68825576d19f8aaedb01b1b148cfa (patch)
tree4eef2f13896adc215f26e24d89f0bec18890aaad /rs/java/android/renderscript/ProgramFragment.java
parent620d6c0201a058971565c21445d0ccf44cc4279c (diff)
wifi: deprecated PSK_SAE_TRANSITION and OWE_TRANSITION mode
AccessPoints are contructed by WifiTracker, it is created from ScanResult, then associated to a Configuration if it is saved. For Ap supports SAE+PSK, - security of ScanResult is SECURITY_PSK_SAE_TRANSITION, while - security of Configuration is SECURITY_SAE. The Apkey is mismatch between ScanResult and Configuration, hence AccessPoint is not associated to target Configuration. In such case, settings UI takes AccessPoint as unsaved, and ask for password when user clicks connect. When display AP information in GUI, it will check the security and SSID in the Configuration, if both of them match, system think there the same AP will display same state. In such case, when connect to a PSK_SAE_TRANSITION AP, it there is another AP in SECURITY_SAE mode with same SSID and password, it will think the SECURITY_SAE is also connected, it will display two connected AP in the GUI This change deprecate PSK_SAE_TRANSITION and OWE_TRANSITION mode to fix the mismatch between ScanResult and Configuration, only use SAE and OWE instead of PSK_SAE_TRANSITION and OWE_TRANSITION. CRs-Fixed: 2559275 Change-Id: I6275c40463034e0294a30282a711583bce6e2a7d
Diffstat (limited to 'rs/java/android/renderscript/ProgramFragment.java')
0 files changed, 0 insertions, 0 deletions