1163915 - wifi ap set encryption method as "wpa2-psk",but wifi search & connect as "wpa-psk"

Status: RESOLVED DUPLICATE of bug 972156

(Firefox OS Graveyard :: Wifi, defect)

Description

[songbai.chen]

DEFECT DESCRIPTION:
  While wifi ap set encryption method as "wpa2-psk" or "wpa-psk",7715 FFOS can only seach and connect to it as "wpa-psk".

Steps to reproduce:
----------------------------------------------------
Step 1: Set wifi ap encryption method as "wpa2-psk".
Step 2: Open the phone,and search aps.
Step 3: connect to the ap we have set.
Step 4: in the search result list,and also when connected to the ap,the phone display "wpa-psk" as encryption method.


This issue also happened with both FFOS & flame.

Expected result:
---------------------------------------
7715 & flame should properly show the encryption method "wpa2-psk"

Additional info:
--------------------------------------
Reproduce rate:  5/5

Comment 1

[songbai.chen]

vchen & sku,

please help to deal with this issue


thanks！

Comment 2

[:Atoll]

I experienced this issue as well on FOTA eng.naoki.20151007.074137 / 0195b184.

Comment 3

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

[Blocking Requested - why for this release]:
Wrong encryption type misleads end user.

Comment 4

[Mahendra Potharaju [:mahe]]

Tim, Can you check if its just a message or if its an issue and block with right priority. 

Thanks

Comment 5

[Tim Guan-tin Chien [:timdream] (please needinfo)]

Fred could you help?

Comment 6

[[e-mail]]

Set regression-window-wanted, Please help check if it also breaks from 2.2.


@Naoki, is `status-b2g-v2.1: --- → affected` a typo or you did check it in 2.1?


Richard, does the wifi ap connectable when it shows WPA-PSK(which actually WPA2-PSK)?


Also ni Henry so we can check from both gaia/gecko side..

Comment 7

[Pi Wei Cheng [:piwei] (inactive)]

This is a dupe of bug 833236 and bug 972156. Apparently an extremely old bug that's been there since b2g18.

Comment 8

[:Atoll]

My access point doesn't permit configuring into WPA2-PSK *without* WPA-PSK, to the best of my knowledge, so I cannot test this on your behalf. I know that my Foxfood device *does* connect successfully, but I don't know if it's mis-reporting WPA2-PSK as WPA-PSK, or if it's (incorrectly) preferring WPA-PSK over WPA2-PSK. You'll have to test this on a device in a controlled setting, apologies :(

Comment 9

[Henry Chang [:hchang]]

It seems the internal reports no difference for WPA-PSK/WPA2-PSK (as well as WPA-EAP/WPA2-EAP) from day 1 [1]. I wasn't there so I don't know the story at all. For you information:

1) Technically gecko is able to report the most specific security.
2) Neither iOS 9.1 nor AOSP 5.1.1 shows the specific security.
3) WPA2 is based on WAP with stronger encryption algorithm.

https://hg.mozilla.org/mozilla-central/diff/b52d3db4efa7/dom/wifi/nsWifiWorker.js#l1.457

Comment 10

[:Atoll]

From a reporter perspective, I'm perfectly comfortable with this being marked RESOLVED / WORKSFORME, if we decide that this is how it *should* behave and that it's working as designed (and in parity, per comment 29 #2).

Comment 11

[Andrew Overholt [:overholt]]

(In reply to Pi Wei Cheng [:piwei] from comment #7)
> This is a dupe of bug 833236 and bug 972156. Apparently an extremely old bug
> that's been there since b2g18.

You're correct, it's a dupe of bug 972156. Moving nom and discussion there.