mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Andrew Morton <akpm@osdl.org>
Cc: Kylene Jo Hall <kjhall@us.ibm.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	LSM ML <linux-security-module@vger.kernel.org>,
	Dave Safford <safford@us.ibm.com>, Mimi Zohar <zohar@us.ibm.com>,
	Serge Hallyn <sergeh@us.ibm.com>
Subject: Re: [PATCH 0/7] Integrity Service and SLIM
Date: Tue, 19 Sep 2006 21:02:14 +0200	[thread overview]
Message-ID: <20060919190214.GA7210@elf.ucw.cz> (raw)
In-Reply-To: <20060914165113.3067c4b0.akpm@osdl.org>

On Thu 2006-09-14 16:51:13, Andrew Morton wrote:
> On Tue, 12 Sep 2006 10:57:25 -0700
> Kylene Jo Hall <kjhall@us.ibm.com> wrote:
> 
> > This is an updated request for comments on a proposed integrity 
> > service framework and dummy provider, along with SLIM, a low 
> > water-mark mandatory access control LSM module which utilizes the 
> > integrity services as additional input to the access control decisions.
> 
> Having carefully reviewed your code I have come to the firm conclusion that
> it is written in C.  The next step is to put it all in -mm and see if
> anyone shouts at me.

Hmmm, "it is written in C" does not seem like good enough reason to
merge it... right?

I tried to understand what it is good for, but it seems that in
current state it is not much good for anything.

Will IBM work at splitting ssh so that trusted/untrusted portions are
separated?

								Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2006-09-19 22:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-12 17:57 Kylene Jo Hall
2006-09-14 23:51 ` Andrew Morton
2006-09-19 19:02   ` Pavel Machek [this message]
2006-09-26 15:53     ` David Safford
  -- strict thread matches above, loose matches on Subject: below --
2006-08-23 19:05 Kylene Jo Hall

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=20060919190214.GA7210@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@osdl.org \
    --cc=kjhall@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=safford@us.ibm.com \
    --cc=sergeh@us.ibm.com \
    --cc=zohar@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®