Re: [refpolicy] how to enable gconf(arole_dbus_t errors) and all of the gnome goodies

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2009-05-11 at 14:58 -0400, Christopher J. PeBenito wrote:
> 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@xxxxxxxxxx> 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.
> 

Cool, I'll have a look.
(sorry for bringing this up again, 
I've been going crazy with this for a while)

As for the policy, been running it for a while
(without any gnome support) but then decided to
add some sugar and spice to the system.

Justin P. Mattock


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with
the words "unsubscribe selinux" without quotes as the message.

[Index of Archives]     [Selinux Refpolicy]     [Linux SGX]     [Fedora Users]     [Fedora Desktop]     [Yosemite Photos]     [Yosemite Camping]     [Yosemite Campsites]     [KDE Users]     [Gnome Users]

  Powered by Linux