From: "Dr. David Alan Gilbert" <dgilbert@redhat.com> To: Vivek Goyal <vgoyal@redhat.com> Cc: dinechin@redhat.com, virtio-fs@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com Subject: Re: [PATCH v3 4/5] tools/virtiofsd: xattr name mapping examples Date: Tue, 20 Oct 2020 16:34:43 +0100 [thread overview] Message-ID: <20201020153443.GD2962@work-vm> (raw) In-Reply-To: <20201020144041.GC380917@redhat.com> * Vivek Goyal (vgoyal@redhat.com) wrote: > On Wed, Oct 14, 2020 at 07:02:08PM +0100, Dr. David Alan Gilbert (git) wrote: > > From: "Dr. David Alan Gilbert" <dgilbert@redhat.com> > > > > Add a few examples of xattrmaps to the documentation. > > > > Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com> > > --- > > docs/tools/virtiofsd.rst | 50 ++++++++++++++++++++++++++++++++++++++++ > > 1 file changed, 50 insertions(+) > > > > diff --git a/docs/tools/virtiofsd.rst b/docs/tools/virtiofsd.rst > > index a3a120da2f..5cb64612ed 100644 > > --- a/docs/tools/virtiofsd.rst > > +++ b/docs/tools/virtiofsd.rst > > @@ -163,6 +163,56 @@ in which case a 'server' rule will always match on all names from > > the server. > > > > > > +xattr-mapping Examples > > +---------------------- > > + > > +1) Prefix all attributes with 'user.virtiofs.' > > + > > +:: > > + > > +-o xattrmap=":prefix:all::user.virtiofs.::bad:all:::" > > + > > Staring at rule. > > ":bad:all:::" > > and trying to map this to ":type:scope:key:prepend:" > > type==bad > scope==all > key=="" > prepend=="" Correct. > > + > > +This uses two rules, using : as the field separator; > > +the first rule prefixes and strips 'user.virtiofs.', > > +the second rule hides any non-prefixed attributes that > > +the host set. > > What is non-prefixed xattr in this context. If client sends > "security.selinux", is prefixed or non-prefixed. Note that anything originating at the client (i.e. starting with "") will get caught by the first rule and be prefixed with 'user.virtiofs.' This second rule will only be triggered by an xattr name coming from the server (i.e a listxattr) for a name that doesn't begin with user.virtiofs. (i.e. didn't match the 1st rule for a server xattr). This makes sure that only guest created xattr's (that were set and had a prefix added) are then visible to the guest. > Documentation in first patch said. > > +- 'bad' - If a client tries to use this name it's > + denied using EPERM; when the server passes an attribute > + name matching it's hidden. > > I am not sure which xattr name will be blocked if key=="" and prepend=="" All of them; they're still matched at the beginning; as the first patch says 'It maybe empty in which case a 'client' rule will always match on client names' > > +2) Prefix 'trusted.' attributes, allow others through > > + > > +:: > > + > > + "/prefix/all/trusted./user.virtiofs./ > > + /bad/server//trusted./ > > + /bad/client/user.virtiofs.// > > + /ok/all///" > > + > > + > > +Here there are four rules, using / as the field > > +separator, and also demonstrating that new lines can > > +be included between rules. > > +The first rule is the prefixing of 'trusted.' and > > +stripping of 'user.virtiofs.'. > > So this is bidrectional rule, right. For setxattr(), "trusted." > will be replaced with "user.virtiofs" and for listxattr(), > server will replace user.virtiofs with trusted. ? prefixed not replaced; so it'll turn "trusted." into "user.virtiofs.trusted." and strip it back off for listxattr. > > +The second rule hides unprefixed 'trusted.' attributes > > +on the host. > > If host has "trusted.*", we are not hiding it and as per first > rule we are converting it to "user.virtiofs.trusted.*", right? > So why this second rule is needed. No, the first rule will only prefix strings provided by the guest and strip strings provided by the server. This rule hides existing server 'trusted.' xattrs - so if the guest sets trusted.foo it's not confused by also seeing a server trusted.foo > > +The third rule stops a guest from explicitly setting > > +the 'user.viritofs.' path directly. > > +Finally, the fourth rule lets all remaining attributes > > +through. > > So If I don't specify third rule, and client does > setxattr(user.virtiofs.*), it will simply be a passthrough? Right; and that's dangerous, because a non-privileged guest process can set a user. xattr; so a non-priv guest process could set user.virtiofs.trusted.foo and then it would get read back and be used as trusted.foo that has an impact on priviliged processes. Dave > Thanks > Vivek > > > + > > +3) Hide 'security.' attributes, and allow everything else > > + > > +:: > > + > > + "/bad/all/security./security./ > > + /ok/all///' > > + > > +The first rule combines what could be separate client and server > > +rules into a single 'all' rule, matching 'security.' in either > > +client arguments or lists returned from the host. This stops > > +the client seeing any 'security.' attributes on the server and > > +stops it setting any. > > + > > Examples > > -------- > > > > -- > > 2.28.0 > > -- 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: Vivek Goyal <vgoyal@redhat.com> Cc: dinechin@redhat.com, virtio-fs@redhat.com, qemu-devel@nongnu.org Subject: Re: [Virtio-fs] [PATCH v3 4/5] tools/virtiofsd: xattr name mapping examples Date: Tue, 20 Oct 2020 16:34:43 +0100 [thread overview] Message-ID: <20201020153443.GD2962@work-vm> (raw) In-Reply-To: <20201020144041.GC380917@redhat.com> * Vivek Goyal (vgoyal@redhat.com) wrote: > On Wed, Oct 14, 2020 at 07:02:08PM +0100, Dr. David Alan Gilbert (git) wrote: > > From: "Dr. David Alan Gilbert" <dgilbert@redhat.com> > > > > Add a few examples of xattrmaps to the documentation. > > > > Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com> > > --- > > docs/tools/virtiofsd.rst | 50 ++++++++++++++++++++++++++++++++++++++++ > > 1 file changed, 50 insertions(+) > > > > diff --git a/docs/tools/virtiofsd.rst b/docs/tools/virtiofsd.rst > > index a3a120da2f..5cb64612ed 100644 > > --- a/docs/tools/virtiofsd.rst > > +++ b/docs/tools/virtiofsd.rst > > @@ -163,6 +163,56 @@ in which case a 'server' rule will always match on all names from > > the server. > > > > > > +xattr-mapping Examples > > +---------------------- > > + > > +1) Prefix all attributes with 'user.virtiofs.' > > + > > +:: > > + > > +-o xattrmap=":prefix:all::user.virtiofs.::bad:all:::" > > + > > Staring at rule. > > ":bad:all:::" > > and trying to map this to ":type:scope:key:prepend:" > > type==bad > scope==all > key=="" > prepend=="" Correct. > > + > > +This uses two rules, using : as the field separator; > > +the first rule prefixes and strips 'user.virtiofs.', > > +the second rule hides any non-prefixed attributes that > > +the host set. > > What is non-prefixed xattr in this context. If client sends > "security.selinux", is prefixed or non-prefixed. Note that anything originating at the client (i.e. starting with "") will get caught by the first rule and be prefixed with 'user.virtiofs.' This second rule will only be triggered by an xattr name coming from the server (i.e a listxattr) for a name that doesn't begin with user.virtiofs. (i.e. didn't match the 1st rule for a server xattr). This makes sure that only guest created xattr's (that were set and had a prefix added) are then visible to the guest. > Documentation in first patch said. > > +- 'bad' - If a client tries to use this name it's > + denied using EPERM; when the server passes an attribute > + name matching it's hidden. > > I am not sure which xattr name will be blocked if key=="" and prepend=="" All of them; they're still matched at the beginning; as the first patch says 'It maybe empty in which case a 'client' rule will always match on client names' > > +2) Prefix 'trusted.' attributes, allow others through > > + > > +:: > > + > > + "/prefix/all/trusted./user.virtiofs./ > > + /bad/server//trusted./ > > + /bad/client/user.virtiofs.// > > + /ok/all///" > > + > > + > > +Here there are four rules, using / as the field > > +separator, and also demonstrating that new lines can > > +be included between rules. > > +The first rule is the prefixing of 'trusted.' and > > +stripping of 'user.virtiofs.'. > > So this is bidrectional rule, right. For setxattr(), "trusted." > will be replaced with "user.virtiofs" and for listxattr(), > server will replace user.virtiofs with trusted. ? prefixed not replaced; so it'll turn "trusted." into "user.virtiofs.trusted." and strip it back off for listxattr. > > +The second rule hides unprefixed 'trusted.' attributes > > +on the host. > > If host has "trusted.*", we are not hiding it and as per first > rule we are converting it to "user.virtiofs.trusted.*", right? > So why this second rule is needed. No, the first rule will only prefix strings provided by the guest and strip strings provided by the server. This rule hides existing server 'trusted.' xattrs - so if the guest sets trusted.foo it's not confused by also seeing a server trusted.foo > > +The third rule stops a guest from explicitly setting > > +the 'user.viritofs.' path directly. > > +Finally, the fourth rule lets all remaining attributes > > +through. > > So If I don't specify third rule, and client does > setxattr(user.virtiofs.*), it will simply be a passthrough? Right; and that's dangerous, because a non-privileged guest process can set a user. xattr; so a non-priv guest process could set user.virtiofs.trusted.foo and then it would get read back and be used as trusted.foo that has an impact on priviliged processes. Dave > Thanks > Vivek > > > + > > +3) Hide 'security.' attributes, and allow everything else > > + > > +:: > > + > > + "/bad/all/security./security./ > > + /ok/all///' > > + > > +The first rule combines what could be separate client and server > > +rules into a single 'all' rule, matching 'security.' in either > > +client arguments or lists returned from the host. This stops > > +the client seeing any 'security.' attributes on the server and > > +stops it setting any. > > + > > Examples > > -------- > > > > -- > > 2.28.0 > > -- Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2020-10-20 15:36 UTC|newest] Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-14 18:02 [PATCH v3 0/5] virtiofsd xattr name mappings Dr. David Alan Gilbert (git) 2020-10-14 18:02 ` [Virtio-fs] " Dr. David Alan Gilbert (git) 2020-10-14 18:02 ` [PATCH v3 1/5] tools/virtiofsd: xattr name mappings: Add option Dr. David Alan Gilbert (git) 2020-10-14 18:02 ` [Virtio-fs] " Dr. David Alan Gilbert (git) 2020-10-20 9:07 ` Stefan Hajnoczi 2020-10-20 9:07 ` [Virtio-fs] " Stefan Hajnoczi 2020-10-21 17:13 ` Dr. David Alan Gilbert 2020-10-21 17:13 ` [Virtio-fs] " Dr. David Alan Gilbert 2020-10-20 14:04 ` Vivek Goyal 2020-10-20 14:04 ` [Virtio-fs] " Vivek Goyal 2020-10-22 14:52 ` Vivek Goyal 2020-10-22 14:52 ` [Virtio-fs] " Vivek Goyal 2020-10-23 15:46 ` Dr. David Alan Gilbert 2020-10-23 15:46 ` [Virtio-fs] " Dr. David Alan Gilbert 2020-10-14 18:02 ` [PATCH v3 2/5] tools/virtiofsd: xattr name mappings: Map client xattr names Dr. David Alan Gilbert (git) 2020-10-14 18:02 ` [Virtio-fs] " Dr. David Alan Gilbert (git) 2020-10-20 9:16 ` Stefan Hajnoczi 2020-10-20 9:16 ` [Virtio-fs] " Stefan Hajnoczi 2020-10-22 15:28 ` Vivek Goyal 2020-10-22 15:28 ` [Virtio-fs] " Vivek Goyal 2020-10-23 15:04 ` Dr. David Alan Gilbert 2020-10-23 15:04 ` [Virtio-fs] " Dr. David Alan Gilbert 2020-10-14 18:02 ` [PATCH v3 3/5] tools/virtiofsd: xattr name mappings: Map server " Dr. David Alan Gilbert (git) 2020-10-14 18:02 ` [Virtio-fs] " Dr. David Alan Gilbert (git) 2020-10-15 23:57 ` [Virtio-fs] Puzzle about rootflags, restorecon "operation not supported" Harry G. Coin 2020-10-20 9:54 ` Stefan Hajnoczi 2020-10-20 12:57 ` Miklos Szeredi 2020-10-20 14:55 ` Harry G. Coin 2020-10-20 9:52 ` [PATCH v3 3/5] tools/virtiofsd: xattr name mappings: Map server xattr names Stefan Hajnoczi 2020-10-20 9:52 ` [Virtio-fs] " Stefan Hajnoczi 2020-10-22 16:16 ` Vivek Goyal 2020-10-22 16:16 ` [Virtio-fs] " Vivek Goyal 2020-10-23 14:49 ` Dr. David Alan Gilbert 2020-10-23 14:49 ` [Virtio-fs] " Dr. David Alan Gilbert 2020-10-14 18:02 ` [PATCH v3 4/5] tools/virtiofsd: xattr name mapping examples Dr. David Alan Gilbert (git) 2020-10-14 18:02 ` [Virtio-fs] " Dr. David Alan Gilbert (git) 2020-10-20 9:56 ` Stefan Hajnoczi 2020-10-20 9:56 ` [Virtio-fs] " Stefan Hajnoczi 2020-10-20 14:40 ` Vivek Goyal 2020-10-20 14:40 ` [Virtio-fs] " Vivek Goyal 2020-10-20 15:34 ` Dr. David Alan Gilbert [this message] 2020-10-20 15:34 ` Dr. David Alan Gilbert 2020-10-20 17:56 ` Vivek Goyal 2020-10-20 17:56 ` [Virtio-fs] " Vivek Goyal 2020-10-20 19:02 ` Dr. David Alan Gilbert 2020-10-20 19:02 ` [Virtio-fs] " Dr. David Alan Gilbert 2020-10-21 13:44 ` Vivek Goyal 2020-10-21 13:44 ` [Virtio-fs] " Vivek Goyal 2020-10-21 17:39 ` Dr. David Alan Gilbert 2020-10-21 17:39 ` [Virtio-fs] " Dr. David Alan Gilbert 2020-10-14 18:02 ` [PATCH v3 5/5] tools/virtiofsd: xattr name mappings: Simple 'map' Dr. David Alan Gilbert (git) 2020-10-14 18:02 ` [Virtio-fs] " Dr. David Alan Gilbert (git) 2020-10-20 10:09 ` Stefan Hajnoczi 2020-10-20 10:09 ` [Virtio-fs] " Stefan Hajnoczi 2020-10-20 11:35 ` Dr. David Alan Gilbert 2020-10-20 11:35 ` [Virtio-fs] " Dr. David Alan Gilbert 2020-10-22 13:42 ` Vivek Goyal 2020-10-22 13:42 ` [Virtio-fs] " Vivek Goyal 2020-10-23 13:05 ` Dr. David Alan Gilbert 2020-10-23 13:05 ` [Virtio-fs] " Dr. David Alan Gilbert
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=20201020153443.GD2962@work-vm \ --to=dgilbert@redhat.com \ --cc=dinechin@redhat.com \ --cc=qemu-devel@nongnu.org \ --cc=stefanha@redhat.com \ --cc=vgoyal@redhat.com \ --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: linkBe 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.