NetworkManager and "illegal" SSID chars = crash?
ianburrell at gmail.com
Wed Sep 5 19:27:33 UTC 2007
On 9/5/07, Richi Plana <myfedora at richip.dhs.org> wrote:
> On Wed, 2007-09-05 at 12:59 -0400, Dan Williams wrote:
> > Right; it is an NM issue. If NM crashes or misbehaves with a weird
> > SSID, we need to fix it.
> > As specified in the 802.11 standard, the ESSID is a 32-byte byte array,
> > there are no restrictions made as to what content that 32-bytes may
> > contain. It is up to the program to attempt to coerce that value into
> > something to present to the user.
> Since no semantics has been proposed, then it stands to reason that one
> can just assume 1 byte = 1 character and a straight "byte value =
> Unicode value" conversion should be adopted, right? (No codepage
That would be ISO-8859-1 encoding since Unicode < U+00FF is equal to ISO-8859-1.
> Come to think of it, if they're just a generic 32-byte byte array, why
> even convert them to strings? They only make sense if they happen to
> contain alphanumeric and some symbolic characters (which isn't even a
> convention or restriction). Alright, maybe it's useful for displaying to
> humans when they just happen to be alphanumeric. Forget I asked.
More information about the fedora-devel-list