From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org,
"Richard W . M . Jones" <rjones@redhat.com>
Subject: Re: [PATCH v3 2/2] docs: replace insecure /tmp examples in qsd docs
Date: Mon, 1 Mar 2021 18:28:17 +0000 [thread overview]
Message-ID: <YD0yQaCV7K5cux/H@redhat.com> (raw)
In-Reply-To: <20210301172728.135331-3-stefanha@redhat.com>
On Mon, Mar 01, 2021 at 05:27:28PM +0000, Stefan Hajnoczi wrote:
> World-writeable directories have security issues. Avoid showing them in
> the documentation since someone might accidentally use them in
> situations where they are insecure.
>
> There tend to be 3 security problems:
> 1. Denial of service. An adversary may be able to create the file
> beforehand, consume all space/inodes, etc to sabotage us.
> 2. Impersonation. An adversary may be able to create a listen socket and
> accept incoming connections that were meant for us.
> 3. Unauthenticated client access. An adversary may be able to connect to
> us if we did not set the uid/gid and permissions correctly.
>
> These can be prevented or mitigated with private /tmp, carefully setting
> the umask, etc but that requires special action and does not apply to
> all situations. Just avoid using /tmp in examples.
>
> Reported-by: Richard W.M. Jones <rjones@redhat.com>
> Reported-by: Daniel P. Berrangé <berrange@redhat.com>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> docs/tools/qemu-storage-daemon.rst | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-03-01 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 17:27 [PATCH v3 0/2] docs: show how to spawn qemu-storage-daemon with fd passing Stefan Hajnoczi
2021-03-01 17:27 ` [PATCH v3 1/2] " Stefan Hajnoczi
2021-03-01 18:27 ` Daniel P. Berrangé
2021-03-01 17:27 ` [PATCH v3 2/2] docs: replace insecure /tmp examples in qsd docs Stefan Hajnoczi
2021-03-01 18:28 ` Daniel P. Berrangé [this message]
2021-03-01 19:00 ` Richard W.M. Jones
2021-03-03 9:36 ` [PATCH v3 0/2] docs: show how to spawn qemu-storage-daemon with fd passing Kevin Wolf
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=YD0yQaCV7K5cux/H@redhat.com \
--to=berrange@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=stefanha@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 NNTP newsgroup(s).