linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniil Lunev <dlunev@chromium.org>
To: kbusch@kernel.org
Cc: Mario.limonciello@amd.com, axboe@fb.com, campello@google.com,
	hch@lst.de, hughsient@gmail.com, jorgelo@chromium.org,
	linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
	sagi@grimberg.me
Subject: [RFC 0/2] Split out firmware upgrade from CAP_SYS_ADMIN
Date: Fri, 23 Jul 2021 10:59:41 +1000	[thread overview]
Message-ID: <20210723005941.111198-1-dlunev@chromium.org> (raw)
In-Reply-To: <20210218170947.15727-1-mario.limonciello@dell.com>

Signal boost on this thread for we are interested in a mechanism like that to
avoid running firmware updater with root privileges. We are looking into using
the mechanism to be able to update NVMe and SATA devices from a user with
limited permissions, and to tighten the security for eMMC device, which
currently require only RAW_IO capability to perform a firmware upgrade.

      parent reply	other threads:[~2021-07-23  0:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-18 17:09 [RFC 0/2] Split out firmware upgrade from CAP_SYS_ADMIN Mario Limonciello
2021-02-18 17:09 ` [RFC 1/2] capability: Introduce CAP_FIRMWARE_UPGRADE Mario Limonciello
2021-02-18 17:09 ` [RFC 2/2] nvme: Use CAP_FIRMWARE_UPGRADE to check user commands Mario Limonciello
2021-07-23  0:59 ` Daniil Lunev [this message]

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=20210723005941.111198-1-dlunev@chromium.org \
    --to=dlunev@chromium.org \
    --cc=Mario.limonciello@amd.com \
    --cc=axboe@fb.com \
    --cc=campello@google.com \
    --cc=hch@lst.de \
    --cc=hughsient@gmail.com \
    --cc=jorgelo@chromium.org \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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).