[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKdAkRScDtz4_=j=km5N0DkcSkwSb4pPZroaB60Oca8VegTwLg@mail.gmail.com>
Date: Thu, 18 Oct 2018 13:07:10 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
Cc: "Gustavo A. R. Silva" <gustavo@...eddedor.com>,
"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Input: uinput - fix Spectre v1 vulnerability
On Thu, Oct 18, 2018 at 12:43 PM Alan Cox <gnomes@...rguk.ukuu.org.uk> wrote:
>
> On Tue, 16 Oct 2018 20:12:43 +0200
> "Gustavo A. R. Silva" <gustavo@...eddedor.com> wrote:
>
> > On 10/16/18 8:09 PM, Dmitry Torokhov wrote:
> >
> > >
> > > /dev/uinput
> >
> > I've got it. This explains it all. :)
> >
> > > must be 0600, or accessible to equally privileged user, or you'll be opening your system to much mischief.
>
> Still a correct change.
>
> CAP_SYS_RAWIO is not the same as being root, especially in a container.
Giving access to uinput in an unprivileged container is nutty as well.
Thanks.
--
Dmitry
Powered by blists - more mailing lists