All of lore.kernel.org
 help / color / mirror / Atom feed
From: selinux770@tortenboxer.de
To: selinux@tycho.nsa.gov
Date: Thu, 17 Aug 2006 21:57:29 +0200	[thread overview]
Message-ID: <20060817195729.112220@gmx.net> (raw)

Hi there.

I'm trying to enable SELinux on my Nokia 770 Internet Tablet which is running a modified Debian Linux for ARM processors. Until now I have replaced and installed several files and packages, but now I need further guidance. It seems like SELinux is working in some kind of way. But one main problem/question that persists is that i get a
Controlling term:               unknown (Operation not supported)
when doing a sestatus -v.

The "Current context" for user root is system_u:system_r:sshd_t when i log in via ssh.
(uid=0(root) gid=0(root) groups=0(root) context=system_u:system_r:kernel_t)

Within the device (when opening a console or whatever) the "Current context" is system_u:system_r:kernel_t.
(uid=0(root) gid=0(root) groups=0(root) context=system_u:system_r:kernel_t)
Just as many other (nearly all) processes, too.

So my questions:
1. What is the controlling term in sestatus for? What does it mean if it's unknown and how bad is this problem?
2. Are the wrong contexts of users a policy based problem or are they derived by the problem with the controlling term (or even orthers)? I need to know this since I changed much on the device for SELinux and now I'm not sure if I should continue searching missing functionalities within the system or searching for errors in the policy or file labelling.

If you need any more information feel free to ask.

Thanks in advance
Roland Bender

Further information:
~# sestatus -v
SELinux status:                 enabled
SELinuxfs mount:                /selinux
Current mode:                   permissive
Mode from config file:          enforcing
Policy version:                 19
Policy from config file:        .

Process contexts:
Current context:                system_u:system_r:sshd_t
Init context:                   system_u:system_r:init_t

File contexts:
Controlling term:               unknown (Operation not supported)
/etc/passwd                     system_u:object_r:etc_t
/etc/shadow                     system_u:object_r:shadow_t
/bin/bash                       system_u:object_r:shell_exec_t -> system_u:object_r:shell_exec_t
/bin/login                      system_u:object_r:login_exec_t
/bin/sh                         system_u:object_r:bin_t -> system_u:object_r:shell_exec_t
/sbin/init                      system_u:object_r:init_exec_t
/var/lib/install/sbin/sshd      system_u:object_r:sshd_exec_t
/lib/libc.so.6                  system_u:object_r:lib_t -> system_u:object_r:shlib_t
/lib/ld-linux.so.2              system_u:object_r:lib_t -> system_u:object_r:ld_so_t

~# uname -r
2.6.12.3-omap1

-- 


"Feel free" – 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail

--
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.

             reply	other threads:[~2006-08-17 19:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-17 19:57 selinux770 [this message]
2006-08-19 14:04 ` Russell Coker

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=20060817195729.112220@gmx.net \
    --to=selinux770@tortenboxer.de \
    --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.