SELinux Archive on lore.kernel.org
 help / color / Atom feed
From: Stephen Smalley <stephen.smalley.work@gmail.com>
To: Jonathan Lebon <jlebon@redhat.com>
Cc: SElinux list <selinux@vger.kernel.org>
Subject: Re: [PATCH v2] setfiles: clarify documented path resolution behaviour
Date: Thu, 25 Jun 2020 13:31:01 -0400
Message-ID: <CAEjxPJ7AgxQ-3Pst5Ujq2Mc6-vqikR6xC1iRVsL6McX4_FN6nA@mail.gmail.com> (raw)
In-Reply-To: <CAEjxPJ5H4QWQXB53uGtSdxFpqxJUjHYUmTeRKwYsNeHAajwyDQ@mail.gmail.com>

On Mon, Jun 22, 2020 at 8:25 AM Stephen Smalley
<stephen.smalley.work@gmail.com> wrote:
>
> On Thu, Jun 18, 2020 at 3:05 PM Jonathan Lebon <jlebon@redhat.com> wrote:
> >
> > One thing that confused me when investigating
> > https://github.com/SELinuxProject/selinux/issues/248 (i.e.
> > https://github.com/coreos/fedora-coreos-tracker/issues/512) was that the
> > manual page for `setfiles` seemed to imply that paths were fully
> > resolved. This was consistent with the issues above where `setfiles` was
> > failing because the target of the symbolic link didn't exist.
> >
> > But in fact, the wording around symbolic links in
> > `setfiles`/`restorecon` refers actually to whether the parent
> > directories are canonicalized via `realpath(3)` before labeling.
> >
> > Clarify the man pages to explain this.
> >
> > Signed-off-by: Jonathan Lebon <jlebon@redhat.com>
>
> Acked-by: Stephen Smalley <stephen.smalley.work@gmail.com>

Applied.

      reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18 18:22 Jonathan Lebon
2020-06-22 12:25 ` Stephen Smalley
2020-06-25 17:31   ` Stephen Smalley [this message]

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=CAEjxPJ7AgxQ-3Pst5Ujq2Mc6-vqikR6xC1iRVsL6McX4_FN6nA@mail.gmail.com \
    --to=stephen.smalley.work@gmail.com \
    --cc=jlebon@redhat.com \
    --cc=selinux@vger.kernel.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

SELinux Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/selinux/0 selinux/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 selinux selinux/ https://lore.kernel.org/selinux \
		selinux@vger.kernel.org
	public-inbox-index selinux

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.selinux


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git