Received-SPF: pass (google.com: domain of linux-wireless+bounces-4558-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1;
Message-ID: <e7535e82-10dc-4068-960b-bfe7c6b14aee@gmail.com>
Date: Mon, 11 Mar 2024 05:32:18 -0700
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: "open list:MEDIATEK MT76 WIRELESS LAN DRIVER"
 <linux-wireless@vger.kernel.org>
From: James Prestwood <prestwoj@gmail.com>
Subject: iw hex escapes SSID, but not other fields
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

It was reported to me that some of our tooling (which parses iw output) 
fails due to a network using a WPS device name with non utf-8 
characters. I see that for SSID fields there is specific handling for 
escaping non utf8 bytes, but not for the WPS Device Name (nor any other 
fields AFAICT).

Before you rip me a new one for using iw output like this I have since 
removed this and now use IWD's DBus API :) But older versions of the 
software do still parse iw output. Just wanted to report this since iw 
does print to stdout, so it does seem like it should try and escape 
those bytes when possible, like it does for SSIDs.

Side note, I see the JSON patches are progressing which is probably 
going to be the proper way to use iw as an automated tool going forward. 
I haven't looked at those in detail (maybe its already taken care of), 
but the above issue will likely need to be handled since JSON requires 
utf-8.

Thanks,

James