From: David Safford <safford@watson.ibm.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, serue@linux.vnet.ibm.com,
kjhall@linux.vnet.ibm.com, zohar@us.ibm.com
Subject: Re: [Patch 3/7] integrity: EVM as an integrity service provider
Date: Mon, 26 Mar 2007 13:55:15 -0400 [thread overview]
Message-ID: <1174931715.3493.44.camel@localhost.localdomain> (raw)
In-Reply-To: <20070325121321.GA8550@ucw.cz>
On Sun, 2007-03-25 at 12:13 +0000, Pavel Machek wrote:
> > > + The Extended Verification Module is an integrity provider.
> > > + An extensible set of extended attributes, as defined in
> > > + /etc/evm.conf, are HMAC protected against modification
> > > + using the TPM's KERNEL ROOT KEY, if configured, or with a
> > > + pass-phrase. Possible extended attributes include authenticity,
> > > + integrity, and revision level.
>
> What is identity provider good for? Can you explain it a bit more, or
> perhaps point to Doc*/ somewhere?
> Pavel
There are some papers and related userspace code at
http://www.research.ibm.com/gsal/tcpa
which describe the architecture in more detail, but basically this
integrity provider is designed to complement mandatory access control
systems like selinux and slim. Such systems can protect a running system
against on-line attacks, but do not protect against off-line attacks
(booting Knoppix and changing executables or their selinux labels), or
against attacks which find weaknesses in the kernel or the LSM module
itself.
Using a TPM or passphrase, EVM can verify the integrity of all files
(including the kernel and initrd) and their labels before they are
referenced. Using a TPM, EVM/IMA can attest to the integrity of all files
to a third party, even if the kernel or modules have been compromised.
(An attack can block the attestation, but cannot forge valid TPM
signatures.)
In response to customer demand, we are actively working to develop and
test this attestation in enterprise server environments, integrated
with both selinux and AppArmor.
dave
next prev parent reply other threads:[~2007-03-26 17:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 16:09 [Patch 3/7] integrity: EVM as an integrity service provider Mimi Zohar
2007-03-25 8:14 ` Andrew Morton
2007-03-26 18:23 ` Serge E. Hallyn
2007-03-26 20:56 ` Mimi Zohar
2007-03-25 8:16 ` Andrew Morton
2007-03-25 12:13 ` Pavel Machek
2007-03-26 17:55 ` David Safford [this message]
2007-03-22 23:19 ` Pavel Machek
2007-03-27 17:32 ` David Safford
2007-03-26 3:13 ` Mimi Zohar
2007-03-26 5:28 ` Andrew Morton
2007-03-26 11:43 ` Mimi Zohar
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=1174931715.3493.44.camel@localhost.localdomain \
--to=safford@watson.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=kjhall@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=serue@linux.vnet.ibm.com \
--cc=zohar@linux.vnet.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