All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: M A Young <m.a.young@durham.ac.uk>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH 0/4 v2] tools/hotplug: systemd changes for 4.5
Date: Thu, 11 Dec 2014 13:04:24 +0100	[thread overview]
Message-ID: <20141211120424.GA25950@aepfle.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1412111149080.30133@procyon.dur.ac.uk>

On Thu, Dec 11, M A Young wrote:

> Yes, you do need to set explicit selinux permissions when mounting
> /var/lib/xenstored as otherwise it gets a tmpfs selinux context which
> xenstored can't use in enforcing mode.

Is that "enforcing mode" the default? And would it be too cumbersome to
have these context settings in fstab?

> The other selinux issue is that it seems you can't run xenstored through a
> shell script wrapper, because it still has startup shell script selinux
> permissions when it is trying to connect to the sockets, so it doesn't work.
> It does work if you run xenstored directly from the systemd file.

This sounds like xenstored has to parse the possible environment
variables found in sysconfig.xencommons all by itself? Is there perhaps
a way out of the SELinux jail?

Olaf

  reply	other threads:[~2014-12-11 12:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08 10:18 [PATCH 0/4 v2] tools/hotplug: systemd changes for 4.5 Olaf Hering
2014-12-08 10:18 ` [PATCH 1/4] tools/hotplug: remove SELinux options from var-lib-xenstored.mount Olaf Hering
2014-12-08 10:18 ` [PATCH 2/4] tools/hotplug: remove XENSTORED_ROOTDIR from service file Olaf Hering
2014-12-08 10:18 ` [PATCH 3/4] tools/hotplug: remove EnvironmentFile from xen-qemu-dom0-disk-backend.service Olaf Hering
2014-12-08 10:18 ` [PATCH 4/4] tools/hotplug: use xencommons as EnvironmentFile Olaf Hering
2014-12-10 20:42 ` [PATCH 0/4 v2] tools/hotplug: systemd changes for 4.5 Konrad Rzeszutek Wilk
2014-12-11  8:43   ` Olaf Hering
2014-12-11 12:00     ` M A Young
2014-12-11 12:04       ` Olaf Hering [this message]
2014-12-11 12:05         ` Olaf Hering
2014-12-11 12:29           ` M A Young
2014-12-11 19:15         ` Konrad Rzeszutek Wilk
2014-12-11 19:20           ` Olaf Hering
2014-12-12  0:21             ` Konrad Rzeszutek Wilk

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=20141211120424.GA25950@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=m.a.young@durham.ac.uk \
    --cc=xen-devel@lists.xen.org \
    /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.