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: Tue, 24 May 2005 20:47:52 +0200 [thread overview]
Message-ID: <20050524184752.GB2268@elf.ucw.cz> (raw)
In-Reply-To: <Pine.WNT.4.63.0505240841220.3152@laptop>
Hi!
> > * remove all the buffer overflows. I.e. if grub contains buffer
> > overflow in parsing menu.conf... that is not a security hole
> > (as of now) because only administrator can modify menu.conf.
> > With IMA enabled, it would make your certification useless...
>
> Taking your example: Even if you run a buffer-overflow grub, IMA will
> enable remote parties to differentiate between systems that run
> the vulnerable grub and systems that don't. IMA in this case actually
> can put value to running better software.
Yes, but see above: that buffer overflow in grub was *not* a
vulnerability... not until you introduce IMA.
That is my biggest concern. You are completely changing rules for
userland code. Buffer overflow that only root could exploit used to be
okay. It used to be okay to read config files without communicating
with TPM.
Pavel
next prev parent reply other threads:[~2005-05-24 18:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-24 13:45 Reiner Sailer
2005-05-24 18:47 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-25 15:32 Reiner Sailer
2005-05-25 21:58 ` Pavel Machek
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-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=20050524184752.GB2268@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®