Hi,


On Sun, Aug 23, 2015 at 3:32 AM, Steve Litt <slitt@???> wrote:
> On Sat, 22 Aug 2015 23:57:54 +0200
> "tilt!" <tilt@???> wrote:
>
>> Hello,
>>
>> it has come to my attention that an SSID is defined by a
>> (closed) IEEE standard as (I quote inofficial source [1]):
>>
>> > [...] "0-32 octets with arbitrary contents. A 0-length
>> > SSID indicates the wildcard SSID (in probe request
>> > frames for instance)"
>>
>> This means that
>>
>> #1 SSIDs can have length zero.
>> #2 SSIDs can contain the zerobyte.
>>
>> In the context of the CLI Back-En's (E)SSID encoder, this has
>> the following consequences:
>>
>> a) I refuse to support case #1. It is a special case that
(...)
>>
>> b) I am currently unable to support case #2, because the
(...)
>>
>> Ceterum censeo standards should be open.
>
> If somebody's silly enough to put nullbytes in their ESSID or have it
> blank (as opposed to not advertised), then I don't want to use their
> silly setup. I think it's perfectly fine not to support those two IMHO
> ridiculous situations.
>

What about utf-8 encoded (or other encodings like iso-8859-X) strings
with national charaters like "mściągwoń". Will it be supported?
Supported - mean displayed and setting up connection properly?
:)

--
regards
piotr