Messages in this thread | | | From | David Laight <> | Subject | RE: [PATCH v2] kbuild: treat char as always unsigned | Date | Tue, 25 Oct 2022 10:16:24 +0000 |
| |
From: Linus Torvalds > Sent: 24 October 2022 18:11 ... > > As far as I know, there are no actual rules for SSID character sets, > and while using utf-8 or something else might cause interoperability > problems, this driver seems to be just confused. If you want to check > for "printable characters", that check is still wrong.
Are SSID even required to be printable at all? While most systems only let you configure 'strings' I don't remember that actually being a requirement. (I've sure I read up on this years ago.)
The frame format will be using an explicit length. So even embedded zeros may be valid!
David
- Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales)
| |