From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 1/1] Without allow siginh, we get a huge timeout wait period (15 seconds)
Date: Wed, 16 Feb 2011 09:31:00 -0500 [thread overview]
Message-ID: <4D5BDFA4.2090400@tresys.com> (raw)
In-Reply-To: <20110214190352.GC13533@siphos.be>
On 02/14/11 14:03, Sven Vermeulen wrote:
> On Mon, Feb 14, 2011 at 09:44:04AM -0500, Christopher J. PeBenito wrote:
>> On 2/6/2011 10:16 AM, Sven Vermeulen wrote:
>>> We need to allow siginh; without it, xinit waits for 15 seconds
>>> before continuing (not really user friendly), even though the system
>>> functions properly afterwards.
>>
>> This needs a comment in the policy. Also, it should probably go in
>> xserver_restricted_role() instead.
>
> Why not both (xserver_role and xserver_restricted_role)? Both get the timeout otherwise.
xserver_role() calls xserver_restricted_role().
> I'm trying to find some information on the SIGINH but am failing
> tremendously (all that I can find is that SELinux dontaudit's it and the
> fact that many people don't know that). What is siginh?
Signal inheritance across exec().
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2011-02-16 14:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 15:16 [refpolicy] [PATCH 1/1] Without allow siginh, we get a huge timeout wait period (15 seconds) Sven Vermeulen
2011-02-06 16:48 ` Dominick Grift
2011-02-14 14:44 ` Christopher J. PeBenito
2011-02-14 19:03 ` Sven Vermeulen
2011-02-16 14:31 ` Christopher J. PeBenito [this message]
2011-02-16 14:45 ` Christopher J. PeBenito
2011-02-16 14:59 ` Stephen Smalley
2011-02-22 20:30 ` [refpolicy] [PATCH v2 " Sven Vermeulen
2011-03-03 14:22 ` Christopher J. PeBenito
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=4D5BDFA4.2090400@tresys.com \
--to=cpebenito@tresys.com \
--cc=refpolicy@oss.tresys.com \
/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.