|
Bugzilla – Full Text Bug Listing |
| Summary: | Error in ifup-wireless if special character in WPA-PSK Passphrase | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Christoph Weidmann <c_weidmann> |
| Component: | Network | Assignee: | Joachim Gleissner <joachim.gleissner> |
| Status: | VERIFIED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | heiko.rommel, mjp-novell, mvidner |
| Version: | RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | output of rcnetwork start | ||
Created attachment 50485 [details]
output of rcnetwork start
Hope it helps... The displayed password "(NH4)2SO4" (Ammonium sulphate) is not
x'ed out, because it was for testing purposes only
Please edit /etc/sysconfig/network/scripts/ifup-wireless in line 515 and replace the '/' with '//'. Now it should work. Works! Thanks a lot for caring about. Will this be included in final or does it break anything? Christoph One questtion again: Should or can I change bug-status to "fixed" or should this only be done by novell employees? Usually the assignee sets the bug to "resolved". There are exceptions but in this case please do not set it to "fixed", as it is simply not fixed in our product yet. Please provide an update: Maintenance-Tracker-2700 There is a similar problem that should be mentioned here with SSID names. I noticed when I named my wireless network "Elliott's place" the value in my ifcfg file was: WIRELESS_ESSID='Elliott's place' This should be fixed so that any valid character can be used here. I wish I could have a link here to a web page that explained what characters were valid, but I can't find one. Yes, using apostrophes here will not work. Martin, could you prevent YaST from accepting these? I can prohibit apostrophes when entering the ESSID. That would avoid the problem that ini-agent does not escape the values: bug 72164. *** Bug 136876 has been marked as a duplicate of this bug. *** What is the status here? I have disabled entering the apostrophe to ESSID in yast2-network-2.13.15. So can we close this bug? What about my initial problem with the ( and ) characters? (Klammer in german, don't know how its called in english). Did the fix from comment #2 made his way into comming product? The fix for 136876 is not complete (tested with 0a4ee38a8b35449ab7bbe9e42bd380b6). But when entering " 'L#(UIIII) L " as a WPA_PSK in the YaST2 configuration frontend, the "'" is silently dropped from the input. This should not happen. The user should get some feedback about which characters are not allowed in that situation. This Bugfix is included in SWAMP 2965. Because of the fact that this one includes a bunch of fixes I will wait until this one is fixed. Joachim? Can you give me an update? released *** Bug 145224 has been marked as a duplicate of this bug. *** |
When I'm trying to connect to a WPA-secured WLAN using a chemical formula as Passphrase (because of the mix of digits and characters ;)) I get the following error if this formula contains the "(" sign. First, Ithought this isn't an allowed character, but I'm quite sure that it worked in 9.3.