All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominick Grift <dominick.grift@defensec.nl>
To: Peter Whittaker <peterwhittaker@sphyrnasecurity.com>
Cc: Topi Miettinen <toiwoton@gmail.com>,
	SElinux list <selinux@vger.kernel.org>
Subject: Re: Defining SELinux users, "Unable to get valid context...". Help!
Date: Sun, 14 Feb 2021 17:37:07 +0100	[thread overview]
Message-ID: <ypjl5z2uobbg.fsf@defensec.nl> (raw)
In-Reply-To: <ypjla6s6obit.fsf@defensec.nl> (Dominick Grift's message of "Sun, 14 Feb 2021 17:32:42 +0100")

Dominick Grift <dominick.grift@defensec.nl> writes:

> Peter Whittaker <peterwhittaker@sphyrnasecurity.com> writes:
>
>> On Sun, Feb 14, 2021 at 2:32 AM Dominick Grift
>> <dominick.grift@defensec.nl> wrote:
>>> Peter Whittaker <peterwhittaker@sphyrnasecurity.com> writes:
>>>
>>> > Yes, I may need it, but at this point I want to understand why one
>>> > works and the other doesn't.
>>>
>>> I know that the openssh-server in red-hat based distributions has custom
>>> selinux patches.
>>
>> Well. Just fixed it by accident. The relevant line of /etc/pam.d/sshd was
>>
>>     session    required     pam_selinux.so open env_params
>>
>> In an attempt to debug the problem, I changed this to
>>
>>     session    required     pam_selinux.so open select_context
>>
>> PAM did not ask me for a context, but did set the context correctly.
>>
>>     session    required     pam_selinux.so open
>>
>> also worked fine.
>
> oh right! ... yes corner case...
>
> to make it work with env_params you need:
>
> allow xferHigh2Local_t self:context contains;
>
> Sorry for overlooking that
>
>>
>> I need to do some research on this. The env_params option was a system
>> default, I dislike changing system defaults unless I understand why.
>>
>> Now to figure why the auditor's context is failing to be set.

I think this patch is why you need "context containts" when you have
"env_params" set: https://src.fedoraproject.org/rpms/openssh/blob/rawhide/f/openssh-7.8p1-role-mls.patch



>>
>> P
>>
>> Peter Whittaker
>> Director, Business Development
>> www.SphyrnaSecurity.com
>> +1 613 864 5337

-- 
gpg --locate-keys dominick.grift@defensec.nl
Key fingerprint = FCD2 3660 5D6B 9D27 7FC6  E0FF DA7E 521F 10F6 4098
https://sks-keyservers.net/pks/lookup?op=get&search=0xDA7E521F10F64098
Dominick Grift

  reply	other threads:[~2021-02-14 16:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-11 20:12 Defining SELinux users, "Unable to get valid context...". Help! Peter Whittaker
2021-02-11 20:40 ` Fwd: " Peter Whittaker
2021-02-12  7:22 ` Dominick Grift
2021-02-12  7:54   ` Dominick Grift
2021-02-12 21:16     ` Peter Whittaker
2021-02-12 21:49       ` Dominick Grift
2021-02-12 22:43         ` Peter Whittaker
2021-02-13  7:22           ` Dominick Grift
2021-02-13 14:13             ` Peter Whittaker
2021-02-13 16:09               ` Dominick Grift
2021-02-13 18:06                 ` Topi Miettinen
2021-02-13 20:26                   ` Peter Whittaker
2021-02-13 20:39                     ` Dominick Grift
2021-02-13 22:42                       ` Peter Whittaker
2021-02-14  7:30                         ` Dominick Grift
2021-02-14 16:25                           ` Peter Whittaker
2021-02-14 16:32                             ` Dominick Grift
2021-02-14 16:37                               ` Dominick Grift [this message]
2021-02-14 17:02                                 ` Peter Whittaker

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=ypjl5z2uobbg.fsf@defensec.nl \
    --to=dominick.grift@defensec.nl \
    --cc=peterwhittaker@sphyrnasecurity.com \
    --cc=selinux@vger.kernel.org \
    --cc=toiwoton@gmail.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: 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.