Opened 13 years ago
Last modified 8 years ago
#7660 closed bug
Prop #8 WiFi (WPA,WPA2 encryption) — at Version 9
Reported by: | scottmc | Owned by: | mmlr |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta1 |
Component: | Network & Internet/Wireless | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description (last modified by )
Prop #8 WiFi (WPA,WPA2 encryption)
This was voted as a must-have for Haiku R1 and since a requirement for beta1 is to be feature complete, this is a beta1 blocker.
Developer results
- must-have (nielx, pulkomandy, umccullough, czeidler, jprostko, siarzhuk, jonas.kirilla, scottmc, anevilyak, 3dEyes, stippi, axeld, leavengood, mmlr, yourpalal, mmadia, oruizdorantes, colin, zooey, ithamar, korli, laplace, tqh, phoudoin, bonefish, humdinger, Wim, sikosis, brecht)
- only-if-ready none
General poll results
Change History (9)
comment:1 by , 13 years ago
Description: | modified (diff) |
---|
follow-up: 3 comment:2 by , 12 years ago
follow-up: 4 comment:3 by , 12 years ago
Owner: | changed from | to
---|---|
Status: | new → in-progress |
Replying to scottmc:
Can we call this one complete yet?
Technically yes, as the encryption and authentication is working with the wpa_supplicant in place. But really I'd see this one a bit broader, as in being usable conveniently in everyday scenarios. For this, storing the credentials and some form of sensible auto-connect still needs to be implemented. I'm taking ownership in any case.
follow-up: 5 comment:4 by , 11 years ago
Replying to mmlr:
Replying to scottmc:
Can we call this one complete yet?
Technically yes, as the encryption and authentication is working with the wpa_supplicant in place. But really I'd see this one a bit broader, as in being usable conveniently in everyday scenarios. For this, storing the credentials and some form of sensible auto-connect still needs to be implemented. I'm taking ownership in any case.
How much is left to do on this? Should we add #7663 as a blocker?
comment:5 by , 11 years ago
Replying to scottmc:
Replying to mmlr:
Replying to scottmc:
Can we call this one complete yet?
Technically yes, as the encryption and authentication is working with the wpa_supplicant in place. But really I'd see this one a bit broader, as in being usable conveniently in everyday scenarios. For this, storing the credentials and some form of sensible auto-connect still needs to be implemented. I'm taking ownership in any case.
How much is left to do on this? Should we add #7663 as a blocker?
I believe so..
comment:6 by , 11 years ago
Blocked By: | 7663 added |
---|
comment:7 by , 10 years ago
I think we shouldn't hold this ticket up for #7663, it doesn't make sense.
Is there anything left to implement for WPA/WPA2 specifically?
comment:8 by , 10 years ago
Blocked By: | 7663 removed |
---|
Yes, there are a few problems left:
- Can't join network with special chars (space or so) in the SSID or key
- Network connection is unreliable and will drop after some time, without any notice.
- wpa_supplicant can be crashed easily, and isn't restarted
- if you enter the wrong key and fail connecting to a network, you have to reboot and start over
comment:9 by , 9 years ago
Description: | modified (diff) |
---|
Can we call this one complete yet?