From: guido@trentalancia.com (Guido Trentalancia)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH]: missing file context for system-tools-backends (gnome)
Date: Sun, 24 Jun 2012 03:14:34 +0200 [thread overview]
Message-ID: <1340500474.2822.11.camel@vortex> (raw)
In-Reply-To: <1340446766.1572.12.camel@x220.mydomain.internal>
Hello Dominick.
On Sat, 2012-06-23 at 12:19 +0200, Dominick Grift wrote:
> On Sat, 2012-06-23 at 11:52 +0200, Guido Trentalancia wrote:
>
> > Consider gnome-system-tools is a GUI that is meant to configure network,
> > system users, shared filesystems or folders and system time. That is why
> > we would need a boolean as a lot of people would probably like to
> > disable such administrative functionality in the policy (it is still
> > possible to have the boolean default to true, as in the latest
> > modification sketch that I posted, for a more usable generic system).
> >
> > Can you sketch a few lines of policy modifications for the domain
> > transition that you are talking about ? I guess you want to define a new
> > domain, therefore create a new module for system-tools-backends ? And
> > then allow a domain transition from dbus.te to such domain. And perhaps
> > finally label the system-tools-backends perl script with its
> > own ?_exec_t type instead of the generic binary which is more risky ?
>
> I still can't imagine how this works but:
>
> something like:
>
> type stb_t;
> type stb_exec_t;
> dbus_system_domain(stb_t, stb_exec_t)
> role system_r types stb_t;
>
> and then label the stb executable file(s) type stb_exec_t.
>
> That should tell selinux to perform a domain transition from
> system_busd_t to stb_t on running files with type stb_exec_t.
Yes, more or less what I was imagining.
I would need to test it first and then eventually submit another patch
when possible.
It takes just a little bit more but at least we can get rid of the risky
corecmd_* permissions.
> You can also find me on irc.freenode.org at #selinux or #fedora-selinux
My involvement at the moment is just as a sort of part-time hobbist and
there is a lot more policy and stuff that I'd like to work on, but
unfortunately work constrains do not always allow me to do that.
So, I bet further involvement with other online resources such as irc is
impossible as the list is already considered as heavy load for me at the
moment !
Consider I am also hitting a bug in libsepol when trying to build the
latest policy, so there is a lot of things to sort out and time is very
scarce...
And in reply to what Daniel added, I think Fedora has its own system
configuration tools (for example the system-config-*), so that's
probably the reason why they decided to drop gnome-system-tools and
system-backends-tools if as you say it is not possible to find them
anymore in the latest repository...
Thanks a lot for your comments though !
Regards,
Guido
prev parent reply other threads:[~2012-06-24 1:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 21:03 [refpolicy] [PATCH]: missing file context for system-tools-backends (gnome) Guido Trentalancia
2012-06-21 8:41 ` Dominick Grift
2012-06-21 17:38 ` Guido Trentalancia
2012-06-21 17:58 ` Dominick Grift
2012-06-21 18:06 ` Dominick Grift
2012-06-21 18:41 ` [refpolicy] [PATCH v2]: " Guido Trentalancia
2012-06-21 18:53 ` Daniel J Walsh
2012-06-21 18:27 ` [refpolicy] [PATCH]: " Guido Trentalancia
2012-06-23 8:59 ` Guido Trentalancia
2012-06-23 9:12 ` Dominick Grift
2012-06-23 9:52 ` Guido Trentalancia
2012-06-23 10:19 ` Dominick Grift
2012-06-24 1:14 ` Guido Trentalancia [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=1340500474.2822.11.camel@vortex \
--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.