linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Input: uinput - fix Spectre v1 vulnerability
Date: Thu, 18 Oct 2018 13:07:10 -0700	[thread overview]
Message-ID: <CAKdAkRScDtz4_=j=km5N0DkcSkwSb4pPZroaB60Oca8VegTwLg@mail.gmail.com> (raw)
In-Reply-To: <20181018204344.4c135203@alans-desktop>

On Thu, Oct 18, 2018 at 12:43 PM Alan Cox <gnomes@lxorguk.ukuu.org.uk> wrote:
>
> On Tue, 16 Oct 2018 20:12:43 +0200
> "Gustavo A. R. Silva" <gustavo@embeddedor.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

  reply	other threads:[~2018-10-18 20:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-16 11:13 [PATCH] Input: uinput - fix Spectre v1 vulnerability Gustavo A. R. Silva
2018-10-16 17:21 ` Dmitry Torokhov
2018-10-16 17:52   ` Gustavo A. R. Silva
2018-10-16 18:09     ` Dmitry Torokhov
2018-10-16 18:12       ` Gustavo A. R. Silva
2018-10-18 19:43         ` Alan Cox
2018-10-18 20:07           ` Dmitry Torokhov [this message]
2018-10-22 14:14     ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKdAkRScDtz4_=j=km5N0DkcSkwSb4pPZroaB60Oca8VegTwLg@mail.gmail.com' \
    --to=dmitry.torokhov@gmail.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=gustavo@embeddedor.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).