Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 4 Jan 2017 21:47:04 +0100
From: Greg Kroah-Hartman <>
To: Matthew Garrett <>
Cc: Kees Cook <>,
	Linux Kernel Mailing List <>,
	"Rafael J. Wysocki" <>,
	Len Brown <>, Pavel Machek <>,
	Ulf Hansson <>,
	Mauro Carvalho Chehab <>,
	Tomeu Vizoso <>,
	Lukas Wunner <>,
	Madalin Bucur <>,
	Sudip Mukherjee <>,
	Rasmus Villemoes <>,
	Arnd Bergmann <>,
	Andrew Morton <>,
	Russell King <>,
	Petr Tesarik <>,,
Subject: Re: [PATCH] Allow userspace control of runtime disabling/enabling of
 driver probing

On Wed, Jan 04, 2017 at 02:01:00PM -0600, Matthew Garrett wrote:
> On Wed, Jan 4, 2017 at 1:47 PM, Greg Kroah-Hartman
> <> wrote:
> > You know the device type and vendor/product id before you authorize it,
> > you should be able to do this type of detection otherwise it seems
> > pretty pointless :)
> You know the vendor and product ID, which doesn't tell you whether one
> of the endpoints is a network device or a keyboard. You need to know
> that.

Are you sure you don't have the configuration information as well?  That
should tell you...

And for network devices, they are almost all just vendor/product ids,
not many use the class protocol.


greg k-h

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.