All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: selinux@tycho.nsa.gov, dac.override@gmail.com
Subject: Re: [PATCH] libselinux: add selinux_openssh_contexts_path()
Date: Thu, 21 May 2015 14:02:10 -0400	[thread overview]
Message-ID: <555E1DA2.1030606@tycho.nsa.gov> (raw)
In-Reply-To: <20150521165322.GD683@x131e>

On 05/21/2015 12:53 PM, Dominick Grift wrote:
> On Thu, May 21, 2015 at 06:24:41PM +0200, Dominick Grift wrote:
>> On Thu, May 21, 2015 at 06:14:22PM +0200, Petr Lautrbach wrote:
>>> openssh in Fedora uses "sshd_net_t" type for privilege separated
>>> processes in the preauthentication phase. Similarly, openssh portable uses
>>> "sftp_t" for internal-sftp processes. Both type are hardcoded what is not ideal.
>>> Therefore selinux_openssh_contexts_path() was created to get a path where sshd
>>> can get a correct types prepared by a distribution or an administrator.
>>
>> I requested this feature and i am using this feature in my personal policy. So hereby my ACK for what it is worth.
>>
>> However:
>>
>> That SYSTEMD_CONTEXTS though, that must have been a mistake?
> 
> As far as i am concerned this commit should be reverted:
> 
> https://github.com/SELinuxProject/selinux/commit/ce2a8848ad45e375cfdb58cebe28bc12431bb3db
> 
> I just did a grep -ri systemd_contexts in the systemd repository and nothing returned. I also cannot place that commit message.
> 
>>
>> I do not believe that this is used or that it is needed/wanted.

We can remove it as a separate change, but only if there are no users,
even in legacy distributions, as otherwise it would be an ABI break.

  reply	other threads:[~2015-05-21 18:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21 16:14 [PATCH] libselinux: add selinux_openssh_contexts_path() Petr Lautrbach
2015-05-21 16:24 ` Dominick Grift
2015-05-21 16:53   ` Dominick Grift
2015-05-21 18:02     ` Stephen Smalley [this message]
2015-05-21 18:14       ` Dominick Grift
2015-05-21 16:31 ` Dominick Grift
2015-05-21 17:07   ` Petr Lautrbach
2015-05-21 17:12 ` Stephen Smalley

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=555E1DA2.1030606@tycho.nsa.gov \
    --to=sds@tycho.nsa.gov \
    --cc=dac.override@gmail.com \
    --cc=selinux@tycho.nsa.gov \
    /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.