[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170104091312.GA31129@kroah.com>
Date: Wed, 4 Jan 2017 10:13:12 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Kees Cook <keescook@...omium.org>
Cc: linux-kernel@...r.kernel.org, Matthew Garrett <mjg59@...eos.com>,
kernel-hardening@...ts.openwall.com
Subject: Re: [PATCH] Allow userspace to request device probing even if
defer_all_probes is true
On Tue, Jan 03, 2017 at 03:07:20PM -0800, Kees Cook wrote:
> From: Matthew Garrett <mjg59@...eos.com>
>
> Userspace may wish to make a policy decision to allow certain devices
> to be attached, such as keyboards.
I don't understand what that sentance means. Why wouldn't keyboards be
attached?
> Add a force_probe sysfs node to each device, which if written will
> trigger a probe even if defer_all_probes is currently true.
Why not just manually trigger the bind of the device? I don't
understand the problem here that is being addressed, nor do I understand
how this would be used. More explaination please.
thanks,
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.
