lkml.org 
[lkml]   [2012]   [Dec]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [PATCH] firmware: make sure paths remain relative
From
On Tue, Dec 18, 2012 at 9:37 AM, Kees Cook <keescook@chromium.org> wrote:
> On Mon, Dec 17, 2012 at 5:30 PM, Ming Lei <ming.lei@canonical.com> wrote:
>> On Sat, Dec 15, 2012 at 6:51 AM, Kees Cook <keescook@chromium.org> wrote:
>>> Some devices have configurable firmware locations. If these configuration
>>> mechanisms are exposed to unprivileged userspace, it may be possible to
>>
>> I an wondering how the unprivileged userspace can write the firmware sysfs
>> to trigger loading firmware?
>
> If a daemon were to, for example, make firmware selectable by the user
> (which under certain situations is possible in Chrome OS), it seems
> wasteful require these userspace tools/interfaces to each perform
> filtering, so I figured it would be trivial to put in here instead to
> avoid possible future vulnerabilities.

OK, I understand your concern, and looks reasonable wrt. the specific
problem, and IMO, it is better to provide failure log so that the affected
device driver can be fixed easily.

Thanks,
--
Ming Lei


\
 
 \ /
  Last update: 2012-12-18 04:01    [W:1.863 / U:0.028 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site