All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Michael Tokarev <mjt@tls.msk.ru>,
	Qemu Development List <Qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] 9p mapped-* security model infos are architecture-specific
Date: Wed, 30 Jul 2014 21:55:08 +0530	[thread overview]
Message-ID: <87k36u3jbv.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <53D90245.2050903@msgid.tls.msk.ru>

Michael Tokarev <mjt@tls.msk.ru> writes:

> Apparently the the mapped-* security models results in a raw bytes
> being dumped to host without any architecture normalization (in
> host byte order).  This may even lead to security issues in guest
> when the same files are served from another host for example.
>
> This bug has been initially submitted against debian qemu package, see
> http://bugs.debian.org/755740
>

Thanks for reporting the bug. Yes we do have issue with
mapped-xattr. But mapped-file should be ok. We record the uid/gid as
string in the file.

-aneesh

  reply	other threads:[~2014-07-30 16:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-30 14:33 [Qemu-devel] 9p mapped-* security model infos are architecture-specific Michael Tokarev
2014-07-30 16:25 ` Aneesh Kumar K.V [this message]
2014-07-30 17:43   ` Aneesh Kumar K.V
2014-08-25 11:15     ` Michael Tokarev
2014-08-26  6:10       ` Aneesh Kumar K.V

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=87k36u3jbv.fsf@linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=Qemu-devel@nongnu.org \
    --cc=mjt@tls.msk.ru \
    /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.