From: Rogelio Serrano <rogelio@smsglobal.net>
To: russell@coker.com.au
Cc: selinux@tycho.nsa.gov
Subject: Re: booting in enforcing mode
Date: Sun, 11 Apr 2004 21:35:51 +0800 [thread overview]
Message-ID: <7fd841b7e6c6f8d9ef80c9a1e2f9eb62@debian> (raw)
In-Reply-To: <200404112023.36970.russell@coker.com.au>
On 2004-04-11 18:23:36 +0800 Russell Coker
<russell@coker.com.au> wrote:
> On Sun, 11 Apr 2004 03:28, Rogelio Serrano
> <rogelio@smsglobal.net> wrote:
>> I rewrote mount, syslogd, and klogd to have the bare
>> minimum priviledges.
>
> What did you change?
>
Im using an lfs derived distro. it uses uClibc.
These are all my own versions of those utilities. useful only
from boot scripts. mount is just a wrapper around the mount
syscall. and unmount also a wrapper around the unmount syscall.
they dont need fstab or /proc/mounts. the original versions are
causing too much noise in the logs. i was having lot of
difficulty customizing the policy. i was reading the source
code to find out which permissions were needed and which were
not. i found the original programs to be too complicated for me
to read so I rewrote the easy to rewrite programs so i can
focus on init, login and agetty.
im using busybox for most of the network stuff and logging. in
enforcing mode i was having a lot of difficulty to run syslogd
in the proper context. i was having difficulty with the busybox
code so i ripped out the relevant parts and built my own
syslogd from that. same for klogd. i then tested these programs
and took out some code that caused problems.
Im developing a non standard system. so i can not use the
setools. my only option is to use very simple programs that are
easy to audit and match to the policy which is a stripped down
version of the default policy.
One area im having a lot irritation with is the hotplug
scripts. everytime they run bash opens /proc/kmem /dev/random
/dev/pts /dev/ptmx and countless other devices and files that
is not even mentioned anywhere in the relevant sources. now i
dont know which to allow and which to deny. so now im going to
write small prgrams to replace the scripts.
over all my strategy is to replace or customise programs to
conform to an extermely stringent policy. seems fater that
way.
--
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:[~2004-04-11 13:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-10 7:10 booting in enforcing mode Rogelio Serrano
2004-04-10 14:22 ` Russell Coker
2004-04-10 14:53 ` Rogelio Serrano
2004-04-10 17:28 ` Rogelio Serrano
2004-04-11 10:23 ` Russell Coker
2004-04-11 13:35 ` Rogelio Serrano [this message]
2004-04-12 6:37 ` Russell Coker
2004-04-12 7:10 ` Rogelio Serrano
2004-04-12 10:29 ` Russell Coker
2004-04-11 10:23 ` Russell Coker
2004-04-11 13:41 ` Rogelio Serrano
2004-04-11 14:41 ` Rogelio Serrano
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=7fd841b7e6c6f8d9ef80c9a1e2f9eb62@debian \
--to=rogelio@smsglobal.net \
--cc=russell@coker.com.au \
--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.