linux-kernel - Re: [PATCH 0/2] Add a skeleton module to perform a basic initialization on certain USB devices

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: <alpine.LNX.2.00.1601251511350.21446@cbobk.fhfr.pm>
Date:	Mon, 25 Jan 2016 15:17:09 +0100 (CET)
From:	Jiri Kosina <jikos@...nel.org>
To:	Michal Malý <madcatxster@...oid-pointer.net>
cc:	Bjørn Mork <bjorn@...k.no>,
	gregkh@...uxfoundation.org, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org, dmitry.torokhov@...il.com,
	elias.vds@...il.com, edwin@...ds.nl, simon@...gewell.org
Subject: Re: [PATCH 0/2] Add a skeleton module to perform a basic initialization
 on certain USB devices

On Sat, 23 Jan 2016, Michal Malý wrote:

> I briefly considered leaving the switch up to the userspace and handling the 
> device in the kernel only once it's been switched. I am however uncertain how 
> to advertise this to the users. Writing a tiny app that would currently handle 
> just one device seems like an overkill, abusing usb_modeswitch seems counter-
> intuitive as it's purpose is to handle various USB modems. 

Well, originally usb_modeswitch (beware, it's called "modeswitch", not 
"modemswitch" :) ) was purely for handling ZeroCD on USB 3G modems, and 
it's currently still by far the most common case, but there are other 
devices being handled by that package now; I for example recall some 
HP printers needing a magic USB command to be sent to it before they would 
start printing, and usb_modeswitch is handling those now AFAIK.

So if we do this in userspace, I think usb_modeswitch is not a bad choice.

Thanks,

-- 
Jiri Kosina
SUSE Labs