Bugzilla – Bug 8665
Cannot edit encryption password if changing networks
Last modified: 2008-12-15 12:39:22 UTC
(This is 2 related bugs. Can split if needed.) If I setup Boom to connect to wireless router A and connect to a server there, then later I go back to setup and select wireless router B, the password for router A is present as asterisks. That's bug 1... if I'm changing networks and/or SSIDs it should not try using the same password from another network. Next, while I have that seemingly old password on-screen as asterisks I cannot edit it. That is, I cannot change it in any way to enter a new key. (bug 2)
Doh! I didn't think about bugzilla auto-linking to old bugs. Anyway... The above is with firmware 17, FYI.
This is a longstanding issue. Some devs think there may be another bug for this as well. Do you see many customers complaining about this?
No, I've not heard any customers complain about this.
(In reply to comment #0) > (This is 2 related bugs. Can split if needed.) > If I setup Boom to connect to wireless router A and connect to a server there, > then later I go back to setup and select wireless router B, the password for > router A is present as asterisks. > That's bug 1... if I'm changing networks and/or SSIDs it should not try using > the same password from another network. What difference does it make? It doesn't "try" the password until you've right-arrowed through the existing password. The way I think it should work is that it _should_ display and keep the password for the other network. What if, for example, the password is valid? What if you tried the wrong SSID - you'd loose the password you just entered if you wipe it out automatically just by selecting a different network SSID. The password/asterisks can "go away" as soon as the user begins entering the first character. That, IMO, would be a more elegant way of clearing the old one. > Next, while I have that seemingly old password on-screen as asterisks I cannot > edit it. That is, I cannot change it in any way to enter a new key. (bug 2) Since you can't read the password, I'm not sure what value that might have. Sure, it would be nice if you _know_ that you entered the 17th character incorrectly, but how do you know you didn't also enter the 25th character incorrectly? The only way to do it would be to show the password, but apparently someone decided that's a security risk. It's the security decision that I question. The chances against someone at my home popping out to the network setup and reading my WIFI password and then using that to access my network are astronomically small.
Fixed in rev4532. Will be in SB fw 107, TR fw 55 and Boom fw 19.
Verified functioning properly with r19 & 7.2-22118
This bug has been fixed in the 7.3.0 release version of SqueezeCenter! Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already. If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.