Bug 9690 - unable to enter encryption key (wpa2 64 character hex)
: unable to enter encryption key (wpa2 64 character hex)
Status: CLOSED DUPLICATE of bug 9010
Product: SB Controller
Classification: Unclassified
Component: Setup
: unspecified
: Other Other
: -- normal with 1 vote (vote)
: 7.3
Assigned To: James Richardson
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-10-10 00:49 UTC by michael
Modified: 2012-02-27 17:19 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description michael 2008-10-10 00:49:55 UTC
I'm unable to get the squeezebox controller to talk to my wireless network due to the inability to enter all 64 (hex) characters through the ui.  I only have a hex value for the wap, no ascii equivalent.  I'm not entirely sure the Foundry IronPoint series supports ascii keys. (Yes, I'm sure there's a utility out there somewhere that will hash one for me, if really necessary.) Am I really expected to reconfigure my whole network, generate new keys from an ascii source and keep this ascii duplicate representation around just to use the squeezebox controller?  It's also not very clear that the controller suffers from this odd limitation until you've painstakingly entered 63 characters and reexamined each character again from the start looking for the non-existent typo.  Please add that one last character to the ui entry field and recognize hex entry.
Comment 1 James Richardson 2008-11-11 10:21:37 UTC

*** This bug has been marked as a duplicate of bug 9010 ***
Comment 2 James Richardson 2012-02-27 17:19:09 UTC
Closing resolved bugs - if you feel this bug still exists please first re-test with the latest SW/FW version.  If you are able to reproduce then feel free to reopen and attach new logs / steps to reproduce.