From: Oliver Hookins <oliver.hookins@anchor.com.au>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SELinux@tycho.nsa.gov
Subject: Re: Transitions using su command
Date: Fri, 04 Nov 2005 10:58:44 +1100 [thread overview]
Message-ID: <436AA434.6010003@anchor.com.au> (raw)
In-Reply-To: <1131027701.23420.37.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Thu, 2005-11-03 at 15:29 +1100, Oliver Hookins wrote:
>
>>I'm having some funny behaviour from one of our init scripts. We're
>>running a multi-user tomcat environment, which as part of its init
>>script runs a command like the following:
>>
>>su - $USER -c "$TOMCAT_SCRIPT start < /dev/null >& /dev/null"
>>
>>If you run this as root, replacing the variables with the appropriate
>>values, the command runs as expected without any problems. If you run
>>the init script using the service command it prompts the following:
>>
>>Your default context is user_u:system_r:unconfined_t.
>>
>>Do you want to choose a different one? [n]
>>
>>If you just press enter here, it goes back to the bash prompt and seems
>>to succeed, however it worries me that when run automatically at startup
>>and shutdown it might fail. Is there some sort of transition
>>configuration I am missing, or something I can change to allow this
>>transition?
>
>
> Using 'su' in this manner is a bad idea. Use '/sbin/runuser' instead.
> See /etc/init.d/functions for example usage.
Thanks, that works brilliantly!
--
Regards,
Oliver
--
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.
prev parent reply other threads:[~2005-11-03 23:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 4:29 Transitions using su command Oliver Hookins
2005-11-03 14:21 ` Stephen Smalley
2005-11-03 23:58 ` Oliver Hookins [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=436AA434.6010003@anchor.com.au \
--to=oliver.hookins@anchor.com.au \
--cc=SELinux@tycho.nsa.gov \
--cc=sds@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.