On 05/03/2010 10:32 AM, Stephen Smalley wrote:
On Mon, 2010-05-03 at 10:29 -0700, Justin P. Mattock wrote:
On 05/03/2010 10:02 AM, Stephen Smalley wrote:
On Mon, 2010-05-03 at 09:56 -0700, Justin P. Mattock wrote:
On 05/03/2010 09:31 AM, Stephen Smalley wrote:
On Sun, 2010-05-02 at 21:54 -0700, Justin Mattock wrote:
I've been racking my brain for the last few days on
this one, and seem(for the life of me), have no solution.
at first thought this was opensuse specific, but it's not
i.g. my cblfs systems hit this as well(if not all systems at that).
when adding /etc/initscript somehow SELinux can't figure how to
transistion with the whole SHELL -c thing.
under init.c #800(sysvinit-2.85)
the code is this:
/* See if there is an "initscript" (except in single user mode). */
if (access(INITSCRIPT, R_OK) == 0&& runlevel != 'S') {
/* Build command line using "initscript" */
args[1] = SHELL;
args[2] = INITSCRIPT;
args[3] = ch->id;
args[4] = ch->rlevel;
args[5] = "unknown";
for(f = 0; actions[f].name; f++) {
if (ch->action == actions[f].act) {
args[5] = actions[f].name;
break;
}
}
any ideas why SELinux gets confused with this, and
doesn't want to transistion?
In the above code, you are exec'ing the shell and just passing the
script as an argument, not exec'ing the script. So you need a domain
transition on the shell rather than the script, or you need to perform a
setexecon() in the code.
Thanks for the info on this..
I'll have a look at seeing how todo this
(I enjoy the challenge).
As an example on setexecon() I was looking
at the sulogin.c patch for SELinux, but still
need to figure out how to actually do this.
Well, you can do it without using setexeccon() just by configuring
policy to domain transition from init_t to initrc_t on shell_exec_t.
That's what happens if you enable init_upstart=on. So I think it is
mostly just a matter of making that the default and dropping the legacy
transition to sysadm_t for single-user mode.
what/where is that code at in the policy?
(I've looked but can seem to grep the right word).
system/init.te, line 182:
tunable_policy(`init_upstart',`
corecmd_shell_domtrans(init_t, initrc_t)
',`
# Run the shell in the sysadm role for single-user mode.
# causes problems with upstart
sysadm_shell_domtrans(init_t)
')
As for the dropping the legacy(as mentioned in this post:
http://oss.tresys.com/pipermail/refpolicy/2010-February/002012.html)
Yes, that was the prior discussion.
tough to say... right now(as a learning experience) I'll dive into
sysvinit(because I need to get better at reading/writing code),
as well as do the same for the policy.
o.k. Id have to say that this problem has kicked my
a**..
Anyways at this point I'm still looking into this, but have made
little progress with really finding/figuring out
what is going on.
below are some test cases that I created just to see
what/why the domain transition is not happening..
right now the only test case is the first one, that does
execve /bin/sh /etc/initscript and actually
leaves me in the correct context
(keep in mind all of these test cases crash the boot
process, and probably all of them are done wrong)
1) actually leaves me in the right context after reading
initscript:
cat test8.c
#include <unistd.h>
#include <stdio.h>
#include <stdlib.h>
#include <signal.h>
#define INITSCRIPT "/etc/initscript"
int main(int argc, char **argv)
{
if (access(INITSCRIPT, R_OK) == 0 ) {
setenv("/bin/sh", NULL, 1);
printf("Test.................1\n");
signal(SIGINT, SIG_DFL);
printf("Test.................2\n");
signal(SIGTSTP, SIG_DFL);
printf("Test.................3\n");
signal(SIGQUIT, SIG_DFL);
printf("Test.................4\n");
/*execl("/bin/sh", NULL, NULL);*/
/*printf("Test.................5\n");*/
execve("/etc/initscript", argv, NULL);
printf("Test.................6\n");
/*perror("/bin/sh");*/
return 0;
}
}
2) leaves me in the wrong context:
test1.c
#include <unistd.h>
#include <stdio.h>
#include <stdlib.h>
#include <signal.h>
#define INITSCRIPT "/etc/initscript"
#define SHELL "/bin/sh"
int main()
{
char *args[6];
int f;
char *proc;
if(access(INITSCRIPT, R_OK) == 0) {
args[1] = SHELL;
args[2] = "-c";
args[3] = INITSCRIPT;
args[4] = NULL;
for(f = 0; ; f++) {
/*and yes I know I'm issuing this command twice
*just wanted to see if a for loop had something todo
*with the problem.
*/
if (access(INITSCRIPT, R_OK) == 0) {
execve(args[1], args + 1, NULL);
break;
}
}
args[5] = proc;
args[6] = NULL;
}
}
cat test5.c
#include <unistd.h>
#include <stdio.h>
#include <stdlib.h>
#include <signal.h>
#define INITSCRIPT "/etc/initscript"
#define SHELL "/bin/sh"
int main()
{
int argc;
pid_t child;
child = fork();
char *argv[] = {"-c", INITSCRIPT, NULL };
if(access(INITSCRIPT, R_OK) == 0) {
if(child == 0) {
execve(SHELL, argv, NULL);
return 0;
}
}
}
I've even have taken the whole mechanism off of spawn
and loaded the function after reading inittab, but
for some reason I trigger the wrong context.
At this point the only thing I can think of is
the is_selinux_enabled call for loading the policy which
call's execvp(but was too tired to look at that
call).
--
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.
