From: Eamon Walsh <ewalsh@tycho.nsa.gov>
To: Larry Ross <selinux.larry@gmail.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: "security_compute_sid: invalid context" error when starting/stopping mysqld daemon
Date: Fri, 06 Nov 2009 15:10:50 -0500 [thread overview]
Message-ID: <4AF482CA.4090109@tycho.nsa.gov> (raw)
In-Reply-To: <81092d890911041557u78860e4ar65d2a1eb6964656e@mail.gmail.com>
On 11/04/2009 06:57 PM, Larry Ross wrote:
> I have two selinux users that need to be able to stop and start the
> mysql daemon, which is started by the initialization scripts. When
> the daemon is stopped and started by the secadm_u user, it ends up in
> the context secadm_u:secadm_r:mysqld_t. When it is stopped and
> started by the dbadm_u user, it ends up in the
> dbadm_u:dbadm_r:mysqld_t context. When it is started by the init
> scripts it ends up in the system_u:system_r:mysqld_t domain.
>
> I would like it to alway end up in the system_r:mysqld_t domain, but
> can't seem to find any documentation that describes how to get that to
> work.
>
> If I add a role_transition rule to transition the role to system_r
> when the executable is run:
> role_transition sysadm_r mysqld_safe_exec_t system_r;
> role_transition dbadm_r mysqld_safe_exec_t system_r;
> I end up getting these errors:
>
> Nov 4 15:41:36 localhost kernel: type=1401 audit(1257378096.775:46):
> security_compute_sid: invalid context
> dbadm_u:system_r:mysqld_safe_t:s0 for
> scontext=dbadm_u:dbadm_r:initrc_t:s0
> tcontext=system_u:object_r:mysqld_safe_exec_t:s0 tclass=process
>
> I believe I have the rules that should allow this, but obviously I am
> missing something.
> role dbadm_r types mysqld_safe_t;
> role sysadm_r types mysqld_safe_t;
> role system_r types mysqld_safe_t;
> and this:
> allow initrc_t mysqld_safe_t : process transition ;
> which is what the "security_compute_sid" message looks like it is missing.
>
> Does anyone know where I can find a good description of how to get a
> service to transistion back into system_r when started by a user or
> have any idea what I am missing?
The run_init program was designed to solve this problem, take a look at
the man page.
On Fedora at least, the "service" command calls run_init internally, so
doing "service mysqld start" should in theory start it up in the
system_r role. If you're just running "/etc/init.d/mysld start" it
won't transition.
--
Eamon Walsh
National Security Agency
--
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.
next prev parent reply other threads:[~2009-11-06 20:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 23:57 "security_compute_sid: invalid context" error when starting/stopping mysqld daemon Larry Ross
2009-11-05 9:39 ` Dominick Grift
2009-11-06 20:10 ` Eamon Walsh [this message]
2009-11-06 20:39 ` Larry Ross
2009-11-06 22:11 ` Dominick Grift
2009-11-06 23:23 ` Eamon Walsh
2009-11-09 20:54 ` Larry Ross
2009-11-09 21:27 ` Dominick Grift
2009-11-10 23:54 ` Larry Ross
2009-11-11 0:46 ` Eamon Walsh
2009-11-12 0:59 ` Larry Ross
2009-11-11 9:32 ` Dominick Grift
2009-11-11 9:47 ` 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=4AF482CA.4090109@tycho.nsa.gov \
--to=ewalsh@tycho.nsa.gov \
--cc=selinux.larry@gmail.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.