From: Pavel Machek <pavel@ucw.cz>
To: Reiner Sailer <sailer@us.ibm.com>
Cc: Emilyr@us.ibm.com, James Morris <jmorris@redhat.com>,
Kylene@us.ibm.com, linux-kernel@vger.kernel.org,
linux-security-module@wirex.com, Toml@us.ibm.com,
Valdis.Kletnieks@vt.edu
Subject: Re: [PATCH 2 of 4] ima: related Makefile compile order change and Readme
Date: Wed, 25 May 2005 23:58:27 +0200 [thread overview]
Message-ID: <20050525215827.GB4590@elf.ucw.cz> (raw)
In-Reply-To: <Pine.WNT.4.63.0505251116180.3308@laptop>
Hi!
> > >
> > > If I understand you, then you are claiming that steps (ii) to (v)
> > > introduce buffer overflows in bash or show_etc_issue. How?
> >
> > No, I'm not claiming that. You are certainly *not* introducing any new
> > problems.
> >
> > But some problems that used to be harmless (buffer overrun in
> > show_etc_issue command) are not harmless any more.
>
> How is a buffer overrun in a script/application less "harmless" with IMA?
> Please be specific. Preliminary IMA patches are out on the mailing lists.
>
> The only thing that IMA does with respect to existing known buffer
> overruns is that it enables remote parties to know that there is an application
> with a known buffer overrun if this application/script was measured. Such
> information is sensitive and this is one reason why direct access to the
> measurements are restricted to authorized/trusted parties.
Well, you'll have to add measurement of any security-sensitive config
file, any script, and will have to make sure that all parsing of
system config files does not contain buffer-overrun problems. That's
lot of work before IMA is usefull. It is true you do not make
situation any worse.
Good luck and go ahead.
Pavel
next prev parent reply other threads:[~2005-05-25 21:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 15:32 Reiner Sailer
2005-05-25 21:58 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-25 15:00 Reiner Sailer
2005-05-25 15:06 ` Pavel Machek
2005-05-24 21:17 Reiner Sailer
2005-05-24 22:41 ` Pavel Machek
2005-05-24 13:45 Reiner Sailer
2005-05-24 18:47 ` Pavel Machek
2005-05-23 21:36 Reiner Sailer
2005-05-23 23:44 ` Pavel Machek
2005-05-23 23:59 ` James Morris
2005-05-25 18:06 ` Reiner Sailer
2005-05-23 19:56 Reiner Sailer
2005-05-23 20:39 ` Pavel Machek
2005-05-22 23:59 Reiner Sailer
2005-05-23 4:30 ` James Morris
2005-05-23 4:52 ` Valdis.Kletnieks
2005-05-23 8:58 ` Pavel Machek
2005-05-20 13:36 Reiner Sailer
2005-05-21 6:02 ` Greg KH
2005-05-22 19:37 ` Pavel Machek
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=20050525215827.GB4590@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=Emilyr@us.ibm.com \
--cc=Kylene@us.ibm.com \
--cc=Toml@us.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@wirex.com \
--cc=sailer@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®