From: Dominick Grift <dac.override@gmail.com>
To: selinux@tycho.nsa.gov
Subject: Re: the user space object manager code seems to fragile
Date: Sat, 14 Nov 2015 20:30:41 +0100 [thread overview]
Message-ID: <20151114193040.GB14212@x250> (raw)
In-Reply-To: <20151114180109.GA14212@x250>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On Sat, Nov 14, 2015 at 07:01:09PM +0100, Dominick Grift wrote:
> I want to bring to your attention that the user space object manager
> functionality/code of selinux is fragile and is a challenge
>
Okay my apologies, this particular unordered class issue i just mentioned was my
fault. I accidently declared the access vector in a non-. namespace
Still though:
- - (old known issue) dmesg does not print unknown user space access vector
handling. so it not easy to detect
- - dbus fails (even in permissive mode) because dbus object is not
declared and selinux is enabled
Video of me troubleshooting this issue:
https://www.youtube.com/watch?v=FK-wnweI4YM
I still believe the user space object manager handling could be improved
a great deal.
- --
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
iQGcBAEBCgAGBQJWR4vcAAoJENAR6kfG5xmcnw0MALvLVhLObPxqpROkiXHLqapP
x/sLU1te+g+uivW5D8iFWGOa9vjhxdb6AQtwOhRb1ogR+irx0FU9waoVoyPih1NE
UExWr9cmDQIGm3MxUQiQ/fDBnp7sMO9XgXAtJun0IKssog5hZnjprR72a3gXagWM
tS/LipF9oQY/sUW6/7p8XPuU/OtOcR3MnYTxmSCDBi0nEis7tvHrLmTTUq3MonxT
qacVv9ztoed3RSZxXjm30xR7xcwkapD1nKgnEOCLlKuwmCm2istgtp88HlwO/+ps
hXrFWAbFneBp8BQnMEbJ6rr9jKzoo+BKfk89hZOmnO2IJJ0YE3vr+4U9p59qsV+Y
FPloB4si8HMqM+OrRL3woNkZk00hDlrK3Bvxe88j8ynMOLV7f2hBdavgVc8fAyuJ
yaBoQbt+r6Dh9fwWEs0vjFZTqY3Hy2GGceIa7QrpFSRwEzZX2dhbFGFD4Ls8M69A
z1NLlgZrdiHyeyFrri83OUPs4PqeevTa5W7xt1lLKg==
=mPKd
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2015-11-14 19:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-14 18:01 the user space object manager code seems to fragile Dominick Grift
2015-11-14 19:30 ` Dominick Grift [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=20151114193040.GB14212@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.