netdev - Re: [RFC ethtool] ethtool: mock JSON output for --module-info

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <816b36d3-7e12-4b58-8b99-4e477e76372c@lunn.ch>
Date: Wed, 16 Oct 2024 01:16:10 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Daniel Zahka <daniel.zahka@...il.com>
Cc: mkubecek@...e.cz, netdev@...r.kernel.org,
	Jakub Kicinski <kuba@...nel.org>, idosch@...dia.com,
	danieller@...dia.com
Subject: Re: [RFC ethtool] ethtool: mock JSON output for --module-info

> 6. vendor info is displayed as byte arrays.

> Vendor name                               : Arista Networks
> Vendor PN                                 : QDD-400G-XDR4
> Vendor SN                                 : XKT242211481

>     "vendor_name" : [65, 114, 105, 115, 116, 97, 32, 78, 101, 116, 119, 111,
> 114, 107, 115, 32],
>     "vendor_pn" : [81, 68, 68, 45, 52, 48, 48, 71, 45, 88, 68, 82, 52],
>     "vendor_sn" : [88, 75, 84, 50, 52, 50, 50, 49, 49, 52, 56, 49],

Why use byte arrays? String, maybe UTF-8, would be more natural.

	Andrew