Wireless AP SSIDS/Passwords containing spaces fail in station/installer

[rksh]

When attempting to re-configure my homebrew setup to a home wireless AP with an SSID and Password containing multiple space (0x20) characters.

It may worth checking other corner cases such as %2F, %3F, %21, and even possible unicode.

[rksh]

proposed fix - works in testing, but probably not the most elegant way to do this. Provided as a proof-of-concept since I can't easily write a meaningful test case for this, and testing corner cases requires standing up and reconfiguring an 802.11 AP.

[ruffruffruffie]

Hi there! I'm trying to replicate this issue and I am unable to do so; I've tried with SSIDs & password combinations with roughly 5 spaces. Do you have any additional pointers that I can test this bug with?

[rksh]

oh no, this is going to end up being hardware/implementation specific, isn't it? Will dust off some old wireless hardware and do detailed testing.

setup that's known-bad:
Asus AC1200G WPA2 PSK, latest mfgr. firmware, 2 spaces in the SSID, 4 spaces in the password.
Micropython: esp32-idf3-20200902-v1.13.bin

[rksh]

also worth noting that i'm using zsh under OSX.

[rksh]

OK, finally stood up an old Apple Airport for testing!
SSID: "Antenny Wi-Fi Network"

With the password "Testing^5" - All good.
With the password "test test test" - no dice.

Worth noting that this is an old-as-dirt AP, but Apple has apparently updated it to support WPA2-PSK-CCMP (as registered in Android using WiGLE WiFi Wardriving) - haven't found a way to downshift it to WPA1 or WEP, they're aggressive about forcing pretty good defaults in their Airport Utility suite.

Regardless spaces in the SSID are clearly not the issue (weird!). OK to update the issue title?