From: guido@trentalancia.com (Guido Trentalancia)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH/RFC 8/19]: patch set to update the git reference policy
Date: Tue, 25 Jan 2011 01:03:42 +0100 [thread overview]
Message-ID: <1295913822.1665.28.camel@tesla.lan> (raw)
In-Reply-To: <4D3D8703.8040308@gmail.com>
Hello Dominick !
Just a quick comment on the default_t label/permissions, as I still need
to check the rest of this [8/19] comment...
On Mon, 24/01/2011 at 15.04 +0100, Dominick Grift wrote:
> On 01/24/2011 01:44 AM, Guido Trentalancia wrote:
> > --- refpolicy-git-18012011-dbus-messaging/policy/modules/services/dbus.te 2011-01-23 23:13:48.168284256 +0100
> > +++ refpolicy-git-18012011-dbus/policy/modules/services/dbus.te 2011-01-23 23:11:46.430346876 +0100
> > @@ -52,7 +52,7 @@ ifdef(`enable_mls',`
> >
> > # dac_override: /var/run/dbus is owned by messagebus on Debian
> > # cjp: dac_override should probably go in a distro_debian
> > -allow system_dbusd_t self:capability { dac_override setgid setpcap setuid };
> > +allow system_dbusd_t self:capability { dac_override setgid setpcap setuid sys_ptrace };
> > dontaudit system_dbusd_t self:capability sys_tty_config;
> > allow system_dbusd_t self:process { getattr getsched signal_perms setpgid getcap setcap };
> > allow system_dbusd_t self:fifo_file rw_fifo_file_perms;
> > @@ -111,13 +111,20 @@ auth_read_pam_console_data(system_dbusd_
> > corecmd_list_bin(system_dbusd_t)
> > corecmd_read_bin_pipes(system_dbusd_t)
> > corecmd_read_bin_sockets(system_dbusd_t)
> > +# needed for system-tools-backends
> > +corecmd_exec_shell(system_dbusd_t)
> >
> > domain_use_interactive_fds(system_dbusd_t)
> > domain_read_all_domains_state(system_dbusd_t)
> >
> > +files_search_default(system_dbusd_t)
>
> There should not be able default_t type directories. Thus this shouldnt
> be allowed
>
> > +files_read_default_files(system_dbusd_t)
>
> there should not be any default_t type files. Thus this shouldnt be allowed
The point here is that with the reference policy root's home directory
doesn't get its own label but rather fall back to default_t. This is why
I had created those permissions, although I wasn't completely sure about
it because of course it doesn't appear anywhere else.
On Fedora, it's different as they have patched that as follows (taken
from F14 patch in this example):
diff --exclude-from=exclude -N -u -r
nsaserefpolicy/policy/modules/system/userdomain.fc
serefpolicy-3.9.7/policy/modules/system/userdomain.fc
--- nsaserefpolicy/policy/modules/system/userdomain.fc 2010-10-12
22:42:50.000000000 +0200
+++ serefpolicy-3.9.7/policy/modules/system/userdomain.fc
2010-11-05 14:02:26.959899962 +0100
@@ -1,4 +1,17 @@
HOME_DIR -d
gen_context(system_u:object_r:user_home_dir_t,s0-mls_systemhigh)
+HOME_DIR -l
gen_context(system_u:object_r:user_home_dir_t,s0-mls_systemhigh)
HOME_DIR/.+ gen_context(system_u:object_r:user_home_t,s0)
-
/tmp/gconfd-USER -d gen_context(system_u:object_r:user_tmp_t,s0)
+/root(/.*)? gen_context(system_u:object_r:admin_home_t,s0)
+/root/\.cert(/.*)? gen_context(system_u:object_r:home_cert_t,s0)
+/root/\.debug(/.*)? <<none>>
+/dev/shm/pulse-shm.* gen_context(system_u:object_r:user_tmpfs_t,s0)
+/dev/shm/mono.*
gen_context(system_u:object_r:user_tmpfs_t,s0)
+HOME_DIR/bin(/.*)? gen_context(system_u:object_r:home_bin_t,s0)
+HOME_DIR/local/bin(/.*)?
gen_context(system_u:object_r:home_bin_t,s0)
+HOME_DIR/Audio(/.*)? gen_context(system_u:object_r:audio_home_t,s0)
+HOME_DIR/Music(/.*)? gen_context(system_u:object_r:audio_home_t,s0)
+HOME_DIR/\.cert(/.*)? gen_context(system_u:object_r:home_cert_t,s0)
+HOME_DIR/\.pki(/.*)?
gen_context(system_u:object_r:home_cert_t,s0)
+HOME_DIR/\.gvfs(/.*)? <<none>>
+HOME_DIR/\.debug(/.*)? <<none>>
On Debian, it's also being labelled user_home_t. But when I have
installed the plain reference policy, it didn't label any home directory
at all: the type *_home_t does not appear at all in the "standard" file
contexts. So I thought that was the intended behaviour for the reference
policy. I had just followed the INSTALL document...
What do you say ?
Regards,
Guido
next prev parent reply other threads:[~2011-01-25 0:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 0:44 [refpolicy] [PATCH/RFC 8/19]: patch set to update the git reference policy Guido Trentalancia
2011-01-24 14:04 ` Dominick Grift
2011-01-25 0:03 ` Guido Trentalancia [this message]
2011-01-25 9:28 ` Dominick Grift
2011-01-25 12:05 ` Dominick Grift
2011-01-25 13:57 ` Guido Trentalancia
2011-01-25 19:05 ` Guido Trentalancia
2011-01-25 19:19 ` Dominick Grift
2011-01-26 0:41 ` Guido Trentalancia
2011-01-26 8:17 ` Dominick Grift
2011-01-26 17:28 ` Guido Trentalancia
2011-01-26 17:36 ` Dominick Grift
2011-01-27 0:37 ` Guido Trentalancia
2011-01-27 9:16 ` Dominick Grift
2011-01-27 20:36 ` Guido Trentalancia
2011-01-27 20:42 ` Dominick Grift
2011-01-29 1:32 ` Guido Trentalancia
2011-01-28 17:01 ` Dominick Grift
2011-01-28 18:38 ` Guido Trentalancia
2011-01-28 18:47 ` Dominick Grift
2011-01-29 3:49 ` Guido Trentalancia
2011-01-29 8:31 ` Dominick Grift
2011-01-26 17:49 ` 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=1295913822.1665.28.camel@tesla.lan \
--to=guido@trentalancia.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.