From: Dominick Grift <dominick.grift@defensec.nl>
To: selinux@vger.kernel.org
Subject: Re: strange pam selinux issue
Date: Wed, 4 Mar 2020 08:42:51 +0100 [thread overview]
Message-ID: <20200304074251.GA1032355@brutus.lan> (raw)
In-Reply-To: <20200304072940.GA1026144@brutus.lan>
[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]
On Wed, Mar 04, 2020 at 08:29:40AM +0100, Dominick Grift wrote:
> The easiest way to explain this is as follows.
>
> Consider this scenario:
>
> # seinfo -xuwheel.id
>
> Users: 1
> user wheel.id roles wheel.role level s0 range s0;
>
> # selinuxconlist wheel.id sys.id:sys.role:sys.isid:s0
> wheel.id:wheel.role:user.systemd.subj:s0
>
> Now consider this scenario:
>
> # echo '(userrole wheel.id sys.role)' > hack.cil && semodule -i hack.cil
>
> # seinfo -xuwheel.id
>
> Users: 1
> user wheel.id roles { wheel.role sys.role } level s0 range s0;
>
> Here is the issue:
>
> # selinuxconlist wheel.id sys.id:sys.role:sys.isid:s0
> wheel.id:sys.role:sys.isid:s0
For completeness:
# cat /etc/selinux/dssp3-mcs/contexts/users/wheel.id
sys.role:login.subj:s0 wheel.role:user.subj:s0
sys.role:ssh.daemon.subj:s0 wheel.role:user.ssh.subj:s0
sys.role:sys.isid:s0 wheel.role:user.systemd.subj:s0
--
gpg --locate-keys dominick.grift@defensec.nl
Key fingerprint = FCD2 3660 5D6B 9D27 7FC6 E0FF DA7E 521F 10F6 4098
Dominick Grift
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-03-04 7:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 7:29 strange pam selinux issue Dominick Grift
2020-03-04 7:42 ` Dominick Grift [this message]
2020-03-04 14:22 ` Stephen Smalley
2020-03-04 14:36 ` Dominick Grift
2020-03-04 14:40 ` Dominick Grift
2020-03-04 14:46 ` Stephen Smalley
2020-03-04 15:10 ` Stephen Smalley
2020-03-05 17:33 ` Petr Lautrbach
2020-03-05 17:39 ` Dominick Grift
2020-03-05 17:50 ` Dominick Grift
2020-03-05 18:00 ` Dominick Grift
2020-03-04 14:40 ` Stephen Smalley
2020-03-04 14:47 ` Dominick Grift
2020-03-04 15:19 ` Stephen Smalley
2020-03-04 15:28 ` Dominick Grift
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=20200304074251.GA1032355@brutus.lan \
--to=dominick.grift@defensec.nl \
--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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).