From: Daniel Gil Mayol <daniel.gil-mayol@brunel.de>
To: selinux@tycho.nsa.gov
Subject: Services running into vserver
Date: Thu, 21 Jun 2007 09:35:12 +0200 [thread overview]
Message-ID: <467A2A30.2070905@brunel.de> (raw)
Hello my name is Daniel and I have a question related with the services
running into a vserver.
I have read that for Red Hat Enterprise Linux (v. 4), due to a SELinux
bug the dbus can't send audit messages (here is the link:
http://rhn.redhat.com/errata/RHBA-2006-0049.html ).
I have the services dns and dhcp running in a vserver and the system
doesn't work as expected but no audit messages are logged (I suppose
that these both services uses dbus (messagebus) and don't send denied
messages to audit system). Can I get audit messages without update the
selinux policy (fix the bug)? Obviously, without place the services out
of the vserver :)
I'm writing also test scripts for checking that the services running in
the SELinux system are properly protected. All the services running into
the vserver has a common security context, it means, there is no
difference for dns or dhcp services. Should I write an special test
script only for the vserver, enter into the vserver with "[root@mypc ~]#
vserver VSERVER_NAME enter" and run the script?
Thanks,
Daniel
--
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 reply other threads:[~2007-06-21 7:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 7:35 Daniel Gil Mayol [this message]
2007-06-21 12:23 ` Services running into vserver Stephen Smalley
[not found] ` <467A7993.8020506@brunel.de>
2007-06-21 15:19 ` Stephen Smalley
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=467A2A30.2070905@brunel.de \
--to=daniel.gil-mayol@brunel.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.