Date: Tue, 22 Oct 2024 18:47:32 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Tomek CEDRO <tomek@cedro.info> Cc: hackers@freebsd.org Subject: Re: pyserial.tools.list_port improvement for FreeBSD Message-ID: <202410221847.49MIlXEs014246@critter.freebsd.dk> In-Reply-To: <CAFYkXjk2XUc=N49=XN%2B=VA_G%2BVC4KkYUTdE4G=BQDKD86esUHg@mail.gmail.com> References: <202410210954.49L9s9sD076618@critter.freebsd.dk> <203ADA8C-A4ED-4849-B89D-6D18664D67D0@webweaving.org> <CAFYkXjmzAsxLiRZNM1=A37hXKHrDRud6u0R-odxosmCg0oPMcg@mail.gmail.com> <202410221118.49MBIRSj009090@critter.freebsd.dk> <CAFYkXjk2XUc=N49=XN%2B=VA_G%2BVC4KkYUTdE4G=BQDKD86esUHg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-------- Tomek CEDRO writes: > On the "desc:" in place of ugen I would put "Silicon Labs CP2102N USB > to UART Bridge Controller" as the ugen is in the HWID/LOCATION or > there is a reason to put ugen there? :-) The strings from the USB descriptors are unfortunately not available from devinfo(8) and usbconfig(8) needs root-privs to reveal them. I vaguely recall that the strings are not in devinfo (aka: "newbus") due to valid security concerns about unsafe "strings" like these, but I cannot find any evidence of/from that ancient discussion just now. I do find it inconsistent, that usbconfig(8) cannot function in read-only mode for plain users, given that the information it would reveal is already available for all from dmesg, but this might not be policy but merely an sideeffect of the implementation. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202410221847.49MIlXEs014246>