Comment 9 for bug 210484

Revision history for this message
Bogdan Butnaru (bogdanb) wrote :

Hello again.

I've been doing a bit more testing. I have a SpeedTouch ST706 router/ADSL modem from my ISP and I've tried entering accented letters into its ESSID with only partial success. (The router's web interface itself handles them inconsistently.)

I've tried é, è and ô, but the router converts them randomly to ASCII letters, so I can't test how the network manager would deal with them.

I've also tried others including ș, ț. At one point the router interpreted these as something weird; the terminal, upon when calling "iwlist scan", showed "ș*țnng", with a strange sign instead of the asterisk (pasting in Firefox leads to a "hidden" character, i.e. it's not displayed in this form but when moving the cursor over it with the arrows there's a pause there. I'll paste it here to see what launchpad makes of it: "ș
țnng") On the other hand, the network manager applet prints the character as [001C]-in-a-box. Again something "interesting" must be happening with charset conversions.

On the one hand, network manager successfully connected itself to these networks.

On the other hand, since I can't set arbitrary byte strings for my AP's ESSID, I have no idea if it works in general (especially for byte strings that are certainly not valid for the encoding used on the host computer, in my case UTF-8).

If anyone has an access point that can set arbitrary byte strings for the ESSID, they should try several random values, including some that contain invalid Unicode characters (null bytes, illegal byte sequences, etc.)

Unless someone triggers a bug that way (or I encounter another weird AP), my bug is considered solved.