All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominick Grift <dac.override@gmail.com>
To: selinux@tycho.nsa.gov
Subject: Re: continuation of systemd/SELinux discussion from Github
Date: Wed, 2 Dec 2015 11:31:32 +0100	[thread overview]
Message-ID: <20151202103131.GB1028@x250> (raw)
In-Reply-To: <20151202101801.GA1028@x250>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Wed, Dec 02, 2015 at 11:18:01AM +0100, Dominick Grift wrote:
> Let's continue the discussion here.
> 
> The last answered questionnaire is below, any further questions or
> comments?:
> 

I will start by adding a few comments.

I agree that the SELinux user space object manager support is a bit
fragile and rough edged. (I actually recently sent a message to this
list pointing this out)

Either something is wrong with that support or its documentation.

I noticed that many developer focus a lot on uid=0, and forget that
these day's you do not need access to uid=0 to ruin someones life.

To me, from an SELinux perspective at least, a process is just a process
regardless of the UID it is associated with.

The most common use of SELinux is arguably distributions using it to
enforce their policy on their customers hardware, This is fine but
please remember that some customers which to be able to keep that
discretion to them selves.

I think that means in practice that one should keep that in mind at all
times when something is implemented by not making any assumptions about
whether something is useful or not when that is not appropriate.

You may use access control for one this and I may use if for
another. Your threat model may not align with my threat model.

Let us not forget that SELinux is supposed to be a "flexible" MAC, this
is one of the reasons why we use SELinux and not, say SMACK

Thank you. That is all for now

- -- 
02DFF788
4D30 903A 1CF3 B756 FB48  1514 3148 83A2 02DF F788
https://sks-keyservers.net/pks/lookup?op=get&search=0x314883A202DFF788
Dominick Grift
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQGcBAEBCgAGBQJWXsh/AAoJENAR6kfG5xmcM5sL/2m5mL9S947+4yy82L6SzC1g
GV6vjG1D+FSwa0tMPXNTuYJcLC28TnHv8aYO6v6sadDW4nPsm1li4PxziScdGmzz
/F1WeCaJ8hFXlJYCvVc4brlREiOiz08BlZob1SOpvsVDrgeYIsvI1CTKsRDQP86u
5OsVDgLim5slcq5rFcYN1eAsDj7KpOw9ozyFg2qRWdACw/TageKu0FNnHr6GtCRG
pva3Y4Pp3cmH+vaSiffciypuzy+wKbZdUbEaUp7QIIqHJ5IICbZ8qFw3mLZUtziW
scglWAzrlfhsiwwVusPjPbhhZAcdRJtEPcve/dmfpQRFtImt2FeIWabjMa98QmnY
HPH/2jZJIr/tGz/PIkT4SLsFRc3fl3LdV5lqLO5GGpvWxw0Xq1ke3TV5J8WCSitt
lGnSdkzRqC9sasSOBS5cilUpYeOrq37LOwVLu12kamwxJpIYeBLnur/f6lcrQzSU
OZDlpU3u59i3oyFbFauHe2p7wLbDKGxOpCEsv95Now==
=5gZK
-----END PGP SIGNATURE-----

  reply	other threads:[~2015-12-02 10:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 10:18 continuation of systemd/SELinux discussion from Github Dominick Grift
2015-12-02 10:31 ` Dominick Grift [this message]
2015-12-02 18:20 ` Stephen Smalley
2015-12-02 19:47   ` Dominick Grift
2015-12-02 21:23     ` Stephen Smalley
2015-12-02 21:42       ` Dominick Grift
2015-12-03 16:02       ` Miroslav Grepl
2015-12-03 16:11         ` Stephen Smalley
2015-12-03 17:30           ` Dominick Grift
2015-12-04 15:55           ` Dominick Grift
2015-12-10  9:21           ` Miroslav Grepl
2015-12-03 16:30         ` Dominick Grift
2015-12-03 17:20           ` Dominick Grift
2015-12-03 20:25         ` Dominick Grift
2015-12-02 21:37     ` Dominick Grift
2015-12-02 20:34   ` Dominick Grift
2015-12-03  9:09   ` Laurent Bigonville

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=20151202103131.GB1028@x250 \
    --to=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.