From: "Lorenzo Hernández García-Hierro" <lorenzo@gnu.org>
To: Rik van Riel <riel@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/7] procfs privacy
Date: Mon, 18 Apr 2005 22:18:05 +0200 [thread overview]
Message-ID: <1113855485.17341.130.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0504181600480.11251@chimarrao.boston.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1379 bytes --]
El lun, 18-04-2005 a las 16:01 -0400, Rik van Riel escribió:
> On Mon, 18 Apr 2005, Lorenzo Hernández García-Hierro wrote:
>
> > Adding a "trusted user group"-like configuration option could be useful,
> > as it's done within grsecurity, among that the whole thing might be good
> > to depend on a config. option, but that implies using weird ifdef's and
> > the other folks.
>
> I'd rather see something like this implemented as an LSM
> module - or better yet, an SELinux security policy.
For this purpose I (re)submitted a patch originally made by Serge E.
Hallyn that adds a hook in order to catch task lookups, thus, providing
an easy way to handle and determine when a task can lookup'ed.
It's at:
http://pearls.tuxedo-es.org/patches/lsm/lsm-task_lookup-hook.patch
vSecurity currently provides support for it (optional).
SELinux policy can handle in a much more fine-grained these
restrictions, just that it's still something that not all people can
deploy without some special effort and "tweak up" (if their system
doesn't provide support for it, of course, currently Red Hat has done a
great job in that terms).
>
> There's no need to sprinkle security policy all over the
> kernel.
I completely agree.
Cheers,
--
Lorenzo Hernández García-Hierro <lorenzo@gnu.org>
[1024D/6F2B2DEC] & [2048g/9AE91A22][http://tuxedo-es.org]
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-04-18 20:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-18 18:46 [PATCH 0/7] procfs privacy Lorenzo Hernández García-Hierro
2005-04-18 19:27 ` Rik van Riel
2005-04-18 19:46 ` Lorenzo Hernández García-Hierro
2005-04-18 20:01 ` Rik van Riel
2005-04-18 20:18 ` Lorenzo Hernández García-Hierro [this message]
2005-04-18 20:31 ` 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=1113855485.17341.130.camel@localhost.localdomain \
--to=lorenzo@gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.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.