From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Justin Mattock <justinmattock@gmail.com>
Cc: SE-Linux <selinux@tycho.nsa.gov>, tresys <refpolicy@oss.tresys.com>
Subject: Re: [refpolicy] how to enable gconf(arole_dbus_t errors) and all of the gnome goodies
Date: Mon, 11 May 2009 14:58:25 -0400 [thread overview]
Message-ID: <1242068307.27235.25.camel@gorn> (raw)
In-Reply-To: <dd18b0c30905110751hbc3f36n741bad8e57eeb1be@mail.gmail.com>
On Mon, 2009-05-11 at 07:51 -0700, Justin Mattock wrote:
> On Mon, May 11, 2009 at 5:48 AM, Christopher J. PeBenito
> <cpebenito@tresys.com> wrote:
> > On Fri, 2009-05-08 at 10:49 -0700, Justin P. Mattock wrote:
> >> with the latest policy:
> >> I'm wondering what would be the best way to
> >> allow gconf,evolution,nautilus,etc..
> >>
> >> If I start any of these during boot I'll
> >> get system_dbus_t(which gets allowed)
> >> but if I start evolution, nautilus, etc..
> >> normally once Ive booted up I get an error
> >> with checkpolicy.(due to arole_dbus_t instead of
> >> system_dbus_t)
> >>
> >> Should I try and compile these programs
> >> without orbit support(if possible), gconf support
> >> and dbus support?
> >>
> >> is there a boolean that I'm missing?
> >
> > Can you provide the exact error messages?
> >
> If I start the system, and gather avc's
> for(example) gnom-volume-control
> (some of them below, then write them into the policy)
>
> allow user_dbusd_t default_t:chr_file { read write getattr open ioctl };
> allow user_dbusd_t gconf_etc_t:dir { search getattr };
> allow user_dbusd_t gconf_home_t:dir { write search read remove_name
> open getattr add_name };
> allow user_dbusd_t gconf_home_t:file { rename setattr read create
> write getattr unlink open append };
> allow user_dbusd_t gconfd_exec_t:file { read execute open execute_no_trans };
> allow user_dbusd_t mozilla_t:unix_stream_socket connectto;
> allow user_dbusd_t self:process getsched;
>
> the error is this:
>
> m4 -D enable_mcs -D distro_redhat -D mls_num_sens=16 -D
> mls_num_cats=256 -D mcs_num_cats=256 -D hide_broken_symptoms -D
> self_contained_policy policy/support/file_patterns.spt
> policy/support/ipc_patterns.spt policy/support/loadable_module.spt
> policy/support/misc_macros.spt policy/support/misc_patterns.spt
> policy/support/mls_mcs_macros.spt policy/support/obj_perm_sets.spt
> tmp/generated_definitions.conf policy/global_booleans
> policy/global_tunables > tmp/global_bools.conf
> Creating mcs policy.conf
> cat tmp/pre_te_files.conf tmp/all_attrs_types.conf
> tmp/global_bools.conf tmp/only_te_rules.conf tmp/all_post.conf >
> policy.conf
> Compiling mcs policy.22
> /usr/bin/checkpolicy -M -c 22 -U deny policy.conf -o policy.22
> /usr/bin/checkpolicy: loading policy configuration from policy.conf
> policy/modules/services/xserver.te":1042:ERROR 'type user_dbusd_t is
> not within scope' at token ';' on line 2597865:
>
> allow user_dbusd_t default_t:chr_file { read write getattr open ioctl };
> checkpolicy: error(s) encountered while parsing configuration
> make: *** [policy.22] Error 1
user_dbusd_t is optionally declared, and the invocation is in
policy/modules/roles/unprivuser.te line 37 (in current refpolicy trunk).
You would have to put rules in that optional, otherwise the rule is out
of scope.
--
Chris PeBenito
Tresys Technology, LLC
(410) 290-1411 x150
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
WARNING: multiple messages have this Message-ID (diff)
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] how to enable gconf(arole_dbus_t errors) and all of the gnome goodies
Date: Mon, 11 May 2009 14:58:25 -0400 [thread overview]
Message-ID: <1242068307.27235.25.camel@gorn> (raw)
In-Reply-To: <dd18b0c30905110751hbc3f36n741bad8e57eeb1be@mail.gmail.com>
On Mon, 2009-05-11 at 07:51 -0700, Justin Mattock wrote:
> On Mon, May 11, 2009 at 5:48 AM, Christopher J. PeBenito
> <cpebenito@tresys.com> wrote:
> > On Fri, 2009-05-08 at 10:49 -0700, Justin P. Mattock wrote:
> >> with the latest policy:
> >> I'm wondering what would be the best way to
> >> allow gconf,evolution,nautilus,etc..
> >>
> >> If I start any of these during boot I'll
> >> get system_dbus_t(which gets allowed)
> >> but if I start evolution, nautilus, etc..
> >> normally once Ive booted up I get an error
> >> with checkpolicy.(due to arole_dbus_t instead of
> >> system_dbus_t)
> >>
> >> Should I try and compile these programs
> >> without orbit support(if possible), gconf support
> >> and dbus support?
> >>
> >> is there a boolean that I'm missing?
> >
> > Can you provide the exact error messages?
> >
> If I start the system, and gather avc's
> for(example) gnom-volume-control
> (some of them below, then write them into the policy)
>
> allow user_dbusd_t default_t:chr_file { read write getattr open ioctl };
> allow user_dbusd_t gconf_etc_t:dir { search getattr };
> allow user_dbusd_t gconf_home_t:dir { write search read remove_name
> open getattr add_name };
> allow user_dbusd_t gconf_home_t:file { rename setattr read create
> write getattr unlink open append };
> allow user_dbusd_t gconfd_exec_t:file { read execute open execute_no_trans };
> allow user_dbusd_t mozilla_t:unix_stream_socket connectto;
> allow user_dbusd_t self:process getsched;
>
> the error is this:
>
> m4 -D enable_mcs -D distro_redhat -D mls_num_sens=16 -D
> mls_num_cats=256 -D mcs_num_cats=256 -D hide_broken_symptoms -D
> self_contained_policy policy/support/file_patterns.spt
> policy/support/ipc_patterns.spt policy/support/loadable_module.spt
> policy/support/misc_macros.spt policy/support/misc_patterns.spt
> policy/support/mls_mcs_macros.spt policy/support/obj_perm_sets.spt
> tmp/generated_definitions.conf policy/global_booleans
> policy/global_tunables > tmp/global_bools.conf
> Creating mcs policy.conf
> cat tmp/pre_te_files.conf tmp/all_attrs_types.conf
> tmp/global_bools.conf tmp/only_te_rules.conf tmp/all_post.conf >
> policy.conf
> Compiling mcs policy.22
> /usr/bin/checkpolicy -M -c 22 -U deny policy.conf -o policy.22
> /usr/bin/checkpolicy: loading policy configuration from policy.conf
> policy/modules/services/xserver.te":1042:ERROR 'type user_dbusd_t is
> not within scope' at token ';' on line 2597865:
>
> allow user_dbusd_t default_t:chr_file { read write getattr open ioctl };
> checkpolicy: error(s) encountered while parsing configuration
> make: *** [policy.22] Error 1
user_dbusd_t is optionally declared, and the invocation is in
policy/modules/roles/unprivuser.te line 37 (in current refpolicy trunk).
You would have to put rules in that optional, otherwise the rule is out
of scope.
--
Chris PeBenito
Tresys Technology, LLC
(410) 290-1411 x150
next prev parent reply other threads:[~2009-05-11 18:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 17:49 how to enable gconf(arole_dbus_t errors) and all of the gnome goodies Justin P. Mattock
2009-05-08 17:49 ` [refpolicy] " Justin P. Mattock
2009-05-11 12:48 ` Christopher J. PeBenito
2009-05-11 12:48 ` Christopher J. PeBenito
2009-05-11 14:51 ` Justin Mattock
2009-05-11 14:51 ` Justin Mattock
2009-05-11 18:58 ` Christopher J. PeBenito [this message]
2009-05-11 18:58 ` Christopher J. PeBenito
2009-05-11 19:26 ` Justin P. Mattock
2009-05-11 19:26 ` Justin P. Mattock
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=1242068307.27235.25.camel@gorn \
--to=cpebenito@tresys.com \
--cc=justinmattock@gmail.com \
--cc=refpolicy@oss.tresys.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.