All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Roys <joshua.roys@gtri.gatech.edu>
To: "selinux@tycho.nsa.gov" <selinux@tycho.nsa.gov>
Subject: Re: [RFC][PATCH] mod_selinux: setcon earlier
Date: Mon, 8 Mar 2010 16:22:49 -0500	[thread overview]
Message-ID: <4B956AA9.4040004@gtri.gatech.edu> (raw)
In-Reply-To: <4B949C72.4040104@ak.jp.nec.com>

[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]

On 03/08/2010 01:42 AM, KaiGai Kohei wrote:
>> The current code ends up calling setcon after sockets have been opened,
...
>> noticed issues with labeled networking having the setcon() called after
>> the listening sockets are opened.
> 
> Hmm. The purpose of selinuxServerDomain allows to drop unnecessary
> categories on the starting up time, although mod_selinux.pp set it
> to translate into 's0 - mcs_systemhigh'. So, the listener sockets
> also should be created in the configured domain.
> It seems to me what you pointed out is fair enough.
> 
> However, I cannot agree to change security context of the server
> which it parses the configuration file, because we can call setcon()
> in the open_logs hook earlier than listener sockets are created using
> APR_HOOK_FIRST, not APR_HOOK_MIDDLE.
> 
> Thanks,
> 

Hello,

Do you mean instead of mod_selinux hooking post_config, it would now
hook open_logs?  If so, I think you would have to use something like:
(APR_HOOK_REALLY_FIRST-1), because prefork.c hooks open_logs using
REALLY_FIRST...

Thanks,

Josh


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2719 bytes --]

  reply	other threads:[~2010-03-08 21:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-05 21:46 [RFC][PATCH] mod_selinux: setcon earlier Joshua Roys
2010-03-08  6:42 ` KaiGai Kohei
2010-03-08 21:22   ` Joshua Roys [this message]
2010-03-09  1:02     ` KaiGai Kohei

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=4B956AA9.4040004@gtri.gatech.edu \
    --to=joshua.roys@gtri.gatech.edu \
    --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.