All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Karl MacMillan <kmacmillan@mentalrootkit.com>
Cc: Joshua Brindle <method@manicmethod.com>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	Eric Paris <eparis@redhat.com>,
	selinux@tycho.nsa.gov
Subject: Re: Where to specific the handling of unknown kernel classes and perms
Date: Fri, 04 May 2007 13:19:55 -0400	[thread overview]
Message-ID: <463B6B3B.1030906@redhat.com> (raw)
In-Reply-To: <1178295358.15062.9.camel@localhost.localdomain>

Karl MacMillan wrote:
> On Fri, 2007-05-04 at 11:37 -0400, Daniel J Walsh wrote:
>   
>> Joshua Brindle wrote:
>>     
>>> Stephen Smalley wrote:
>>>       
>
> <snip>
>
>   
>>> Ok, I agree, we can work out how to change it on end systems without 
>>> rebuilding the policy later. This should certainly be a managed 
>>> setting so that we can enforce access control on it and audit if 
>>> necessary.
>>>
>>>       
>
> <snip>
>
>   
>> Is this possible to be a boolean?  Tunable eventually.
>>
>>     
>
> Nope - but it could be an semanage command eventually (which would be
> nice since it would generate audit messages).
>
> Karl
>
>   
Ok my question stunk.  The real question is can we make it easy for the 
user
semanage kernel_deny_unknown=1
Which rebuilds and reloads policy.



--
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.

  reply	other threads:[~2007-05-04 17:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02 21:25 Where to specific the handling of unknown kernel classes and perms Eric Paris
2007-05-03  0:46 ` Joshua Brindle
2007-05-03 12:42   ` Karl MacMillan
2007-05-03 12:46   ` Stephen Smalley
2007-05-03 13:20     ` Joshua Brindle
2007-05-03 13:54       ` Stephen Smalley
2007-05-03 15:31         ` Joshua Brindle
2007-05-04 15:37           ` Daniel J Walsh
2007-05-04 16:15             ` Karl MacMillan
2007-05-04 17:19               ` Daniel J Walsh [this message]
2007-05-03  2:12 ` Joshua Brindle

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=463B6B3B.1030906@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=eparis@redhat.com \
    --cc=kmacmillan@mentalrootkit.com \
    --cc=method@manicmethod.com \
    --cc=sds@tycho.nsa.gov \
    --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.