From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] system_userdomain.patch
Date: Wed, 04 Mar 2009 13:05:13 -0500 [thread overview]
Message-ID: <49AEC2D9.1030800@redhat.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
http://people.fedoraproject.org/~dwalsh/SELinux/F11/system_userdomain.patch
The biggest change in this patch is the addition of the $1_usertype.
Instead of using $1_t for all user access, I use $1_usertype. This
allows me to make $1_java_t == $1_t + { execmem execstack}. Similar for
$1_mono_t.
Changed many templates to interfaces, since they were not defining new
types.
Added labeling for symbolic links of homedirs
Labeling for /dev/shm files.
My labeling of /root
added userhomereader attribute in order to allow tunables within tunables.
Added user_home_type handling so we can define additionaly types to the
home dir and still allow users to manage them. (ssh_home_t for example.)
Removed a couple of old booleans that really do not make sense
user_dmesg? Should be only applied to a particular type staff_t maybe,
not all users. guest_t will never run dmesg.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkmuwtgACgkQrlYvE4MpobNoAwCgjcErx5UIQQS91KBMYMnhAl3F
HlgAoLRQrISDwEe00jx73VWzQnq3sBpI
=TwUE
-----END PGP SIGNATURE-----
next reply other threads:[~2009-03-04 18:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 18:05 Daniel J Walsh [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-11-12 22:18 [refpolicy] system_userdomain.patch Daniel J Walsh
2010-02-12 20:26 ` Christopher J. PeBenito
2010-02-13 12:20 ` Daniel J Walsh
2010-08-26 23:45 Daniel J Walsh
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=49AEC2D9.1030800@redhat.com \
--to=dwalsh@redhat.com \
--cc=refpolicy@oss.tresys.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.