From: Magnus Therning <magnus-work@therning.org>
To: selinux@tycho.nsa.gov
Subject: SELinux on Debian (Sid)
Date: Wed, 9 Jun 2004 16:44:04 +0200 [thread overview]
Message-ID: <20040609144404.GJ5477@philips.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1601 bytes --]
I have run into some problems with getting a Debian box up and running
with SELinux. Maybe someone can offer some insights?
Installing selinux-default-policy failed, make complains about 'chsid'
not being present. These are the problems I run into when trying to
complete the installation of the policies:
1. The makefile in /etc/selinux uses 'chsid'. This is the line:
chsid system_u:object_r:policy_config_t /ss_policy
Apparently that tool has been replaced by 'chcon'.
chcon -u system_u -r object_r -t policy_config_t /ss_policy
On a standard kernel this gave the following error message:
chcon: invalid security context
2. The path to 'load_policy' is wrong in /etc/selinux/Makefile it now
lives in /usr/sbin rather than /usr/bin. Also the variable
LOADPOLICY isn't used at all, instead every reference to
'load_policy' is written like this:
$(BINDIR)/load_policy
A little silly (-:
3. 'make relabel' fails on a standard kernel:
load_policy: security_load_policy failed
After rebooting using my SE-kernel 'make relabel' also fails:
security: policydb magic number 0x8 does not match expected magic number 0xf97cff8c
load_policy: security_load_policy failed
Now I am stuck :-( I simply don't know where to look for a thread to
pull to clean up the mess.
/M
--
Magnus Therning mailto:therning@sourceforge.natlab.research.philips.com
+31-40-2745179 http://pww.innersource.philips.com/magnus/
OpenPGP:0x4FBB2C40
X-Windows: ...The art of incompetence.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-06-09 14:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 14:44 Magnus Therning [this message]
2004-06-09 17:50 ` SELinux on Debian (Sid) Luke Kenneth Casson Leighton
2004-06-10 8:13 ` Russell Coker
2004-06-10 22:04 ` Luke Kenneth Casson Leighton
2004-06-10 12:09 ` Magnus Therning
2004-06-10 21:46 ` Luke Kenneth Casson Leighton
2004-06-10 8:17 ` Russell Coker
2004-06-10 12:03 ` Magnus Therning
2004-06-10 13:53 ` Russell Coker
2004-06-10 21:54 ` Luke Kenneth Casson Leighton
2004-06-11 4:13 ` Russell Coker
2004-06-11 20:40 ` Luke Kenneth Casson Leighton
2004-06-12 2:11 ` Russell Coker
2004-06-12 8:14 ` Luke Kenneth Casson Leighton
2004-06-12 8:15 ` Luke Kenneth Casson Leighton
2004-06-11 23:26 ` Greg Norris
2004-06-12 8:19 ` Russell Coker
2004-06-12 14:37 ` Greg Norris
2004-06-13 0:29 ` Russell Coker
2004-06-13 1:28 ` Greg Norris
2004-06-13 7:54 ` Luke Kenneth Casson Leighton
2004-06-13 15:40 ` Greg Norris
2004-06-13 16:03 ` Greg Norris
2004-06-13 23:26 ` Greg Norris
2004-06-14 3:39 ` Greg Norris
2004-06-14 11:38 ` Russell Coker
2004-06-14 12:31 ` Greg Norris
2004-06-18 19:01 ` Luke Kenneth Casson Leighton
2004-06-13 18:29 ` Luke Kenneth Casson Leighton
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=20040609144404.GJ5477@philips.com \
--to=magnus-work@therning.org \
--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.