From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: virtio-fs@redhat.com, rmohr@redhat.com, qemu-devel@nongnu.org,
vromanso@redhat.com
Subject: Re: [Virtio-fs] [PATCH for-5.1 1/3] virtiofsd: drop CAP_DAC_READ_SEARCH
Date: Wed, 22 Jul 2020 17:51:25 +0100 [thread overview]
Message-ID: <20200722165125.GJ2660@work-vm> (raw)
In-Reply-To: <20200722130206.224898-2-stefanha@redhat.com>
* Stefan Hajnoczi (stefanha@redhat.com) wrote:
> virtiofsd does not need CAP_DAC_READ_SEARCH because it already has
> the more powerful CAP_DAC_OVERRIDE. Drop it from the list of
> capabilities.
>
> This is important because container runtimes may not include
> CAP_DAC_READ_SEARCH by default. This patch allows virtiofsd to reduce
> its capabilities when running inside a Docker container.
>
> Note that CAP_DAC_READ_SEARCH may be necessary again in the future if
> virtiofsd starts using open_by_handle_at(2).
>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Yeh that seems to make sense, and is probably worth having irrespective
of the rest of the series.
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
> tools/virtiofsd/passthrough_ll.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/tools/virtiofsd/passthrough_ll.c b/tools/virtiofsd/passthrough_ll.c
> index 94e0de2d2b..50a164a599 100644
> --- a/tools/virtiofsd/passthrough_ll.c
> +++ b/tools/virtiofsd/passthrough_ll.c
> @@ -2596,7 +2596,6 @@ static void setup_capabilities(char *modcaps_in)
> if (capng_updatev(CAPNG_ADD, CAPNG_PERMITTED | CAPNG_EFFECTIVE,
> CAP_CHOWN,
> CAP_DAC_OVERRIDE,
> - CAP_DAC_READ_SEARCH,
> CAP_FOWNER,
> CAP_FSETID,
> CAP_SETGID,
> --
> 2.26.2
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
WARNING: multiple messages have this Message-ID (diff)
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: virtio-fs@redhat.com, rmohr@redhat.com, qemu-devel@nongnu.org,
vromanso@redhat.com
Subject: Re: [PATCH for-5.1 1/3] virtiofsd: drop CAP_DAC_READ_SEARCH
Date: Wed, 22 Jul 2020 17:51:25 +0100 [thread overview]
Message-ID: <20200722165125.GJ2660@work-vm> (raw)
In-Reply-To: <20200722130206.224898-2-stefanha@redhat.com>
* Stefan Hajnoczi (stefanha@redhat.com) wrote:
> virtiofsd does not need CAP_DAC_READ_SEARCH because it already has
> the more powerful CAP_DAC_OVERRIDE. Drop it from the list of
> capabilities.
>
> This is important because container runtimes may not include
> CAP_DAC_READ_SEARCH by default. This patch allows virtiofsd to reduce
> its capabilities when running inside a Docker container.
>
> Note that CAP_DAC_READ_SEARCH may be necessary again in the future if
> virtiofsd starts using open_by_handle_at(2).
>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Yeh that seems to make sense, and is probably worth having irrespective
of the rest of the series.
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
> tools/virtiofsd/passthrough_ll.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/tools/virtiofsd/passthrough_ll.c b/tools/virtiofsd/passthrough_ll.c
> index 94e0de2d2b..50a164a599 100644
> --- a/tools/virtiofsd/passthrough_ll.c
> +++ b/tools/virtiofsd/passthrough_ll.c
> @@ -2596,7 +2596,6 @@ static void setup_capabilities(char *modcaps_in)
> if (capng_updatev(CAPNG_ADD, CAPNG_PERMITTED | CAPNG_EFFECTIVE,
> CAP_CHOWN,
> CAP_DAC_OVERRIDE,
> - CAP_DAC_READ_SEARCH,
> CAP_FOWNER,
> CAP_FSETID,
> CAP_SETGID,
> --
> 2.26.2
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2020-07-22 16:51 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 13:02 [Virtio-fs] [PATCH for-5.1 0/3] virtiofsd: allow virtiofsd to run in a container Stefan Hajnoczi
2020-07-22 13:02 ` Stefan Hajnoczi
2020-07-22 13:02 ` [Virtio-fs] [PATCH for-5.1 1/3] virtiofsd: drop CAP_DAC_READ_SEARCH Stefan Hajnoczi
2020-07-22 13:02 ` Stefan Hajnoczi
2020-07-22 16:51 ` Dr. David Alan Gilbert [this message]
2020-07-22 16:51 ` Dr. David Alan Gilbert
2020-07-22 13:02 ` [Virtio-fs] [PATCH for-5.1 2/3] virtiofsd: add container-friendly -o chroot sandboxing option Stefan Hajnoczi
2020-07-22 13:02 ` Stefan Hajnoczi
2020-07-22 16:58 ` [Virtio-fs] " Daniel P. Berrangé
2020-07-22 16:58 ` Daniel P. Berrangé
2020-07-23 12:17 ` [Virtio-fs] " Stefan Hajnoczi
2020-07-23 12:17 ` Stefan Hajnoczi
2020-07-22 17:58 ` [Virtio-fs] " Dr. David Alan Gilbert
2020-07-22 17:58 ` Dr. David Alan Gilbert
2020-07-23 12:28 ` [Virtio-fs] " Stefan Hajnoczi
2020-07-23 12:28 ` Stefan Hajnoczi
2020-07-23 13:47 ` [Virtio-fs] " Vivek Goyal
2020-07-23 13:47 ` Vivek Goyal
2020-07-23 15:36 ` Stefan Hajnoczi
2020-07-23 15:36 ` Stefan Hajnoczi
2020-07-22 18:17 ` Vivek Goyal
2020-07-23 12:29 ` Stefan Hajnoczi
2020-07-22 19:03 ` Dr. David Alan Gilbert
2020-07-22 19:03 ` Dr. David Alan Gilbert
2020-07-23 12:32 ` [Virtio-fs] " Stefan Hajnoczi
2020-07-23 12:32 ` Stefan Hajnoczi
2020-07-23 17:55 ` [Virtio-fs] " Dr. David Alan Gilbert
2020-07-23 17:55 ` Dr. David Alan Gilbert
2020-07-24 12:22 ` [Virtio-fs] " Stefan Hajnoczi
2020-07-24 12:22 ` Stefan Hajnoczi
2020-07-22 13:02 ` [Virtio-fs] [PATCH for-5.1 3/3] virtiofsd: probe unshare(CLONE_FS) and print an error Stefan Hajnoczi
2020-07-22 13:02 ` Stefan Hajnoczi
2020-07-22 17:03 ` [Virtio-fs] " Daniel P. Berrangé
2020-07-22 17:03 ` Daniel P. Berrangé
2020-07-23 12:46 ` [Virtio-fs] " Stefan Hajnoczi
2020-07-23 12:46 ` Stefan Hajnoczi
2020-07-23 12:50 ` [Virtio-fs] " Daniel P. Berrangé
2020-07-23 12:50 ` Daniel P. Berrangé
2020-07-23 13:56 ` [Virtio-fs] " Vivek Goyal
2020-07-23 13:56 ` Vivek Goyal
2020-07-23 15:19 ` Stefan Hajnoczi
2020-07-22 18:19 ` [Virtio-fs] [PATCH for-5.1 0/3] virtiofsd: allow virtiofsd to run in a container Vivek Goyal
2020-07-23 12:46 ` Stefan Hajnoczi
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=20200722165125.GJ2660@work-vm \
--to=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rmohr@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtio-fs@redhat.com \
--cc=vromanso@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.