From: virtiofs-bot@sinrega.org
To: virtio-fs@redhat.com
Subject: [Virtio-fs] [virtiofsd] MR opened: passthrough: Replace `openat(2)` with `openat2(2)`
Date: Tue, 18 Oct 2022 19:04:05 +0000 (UTC) [thread overview]
Message-ID: <43656.122101815040209989@us-mta-561.us.mimecast.lan> (raw)
Although it is not a sandboxing solution Using `openat2(2)` with
`RESOLVE_IN_ROOT` and `RESOLVE_NO_MAGICLINKS` add a bit more security
especially if running as non-root and no sandboxing option is available.
This was requested to be able to run inside an OpenShift unprivileged
pod where "virtiofsd is already in a container". The OSP seccomp policy
denies CLONE_NEWUSER and NO_NEW_PRIVILEGES is turn on by default.
This could be useful in combination with !136, related: #63
---
https://gitlab.com/virtio-fs/virtiofsd/-/merge_requests/141
reply other threads:[~2022-10-18 19:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=43656.122101815040209989@us-mta-561.us.mimecast.lan \
--to=virtiofs-bot@sinrega.org \
--cc=virtio-fs@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).