From: Greg KH <greg@kroah.com>
To: Reiner Sailer <sailer@watson.ibm.com>
Cc: linux-kernel@vger.kernel.org,
linux-security-module@mail.wirex.com, kylene@us.ibm.com,
emilyr@us.ibm.com, toml@us.ibm.com
Subject: Re: [PATCH 2 of 4] ima: related Makefile compile order change and Readme
Date: Fri, 20 May 2005 23:02:36 -0700 [thread overview]
Message-ID: <20050521060236.GB24597@kroah.com> (raw)
In-Reply-To: <1116596180.8156.8.camel@secureip.watson.ibm.com>
On Fri, May 20, 2005 at 09:36:20AM -0400, Reiner Sailer wrote:
> The IBM Integrity Measurement Architecture (IMA) builds information
> about the software that was loaded into a system run-time since the
> last reboot. For each loaded executable (binary, kernel module,
> library), the IMA calculates once a SHA1 value over the executable file
> and stores it for later reference. IMA uses (optionally) the Trusted
> Computing Group Trusted Platform Module to protect the integrity of
> the accumulated measurements. IMA can, for example, be used to build
> services that detect compromised malicious software loaded into the
> runtime or can be used to validate expected system configurations.
Do you have any benchmarks with this code running in TPM and non-TPM
mode vs. normal operation?
Also, your coding style has some issues (spaces instead of tabs), {} for
one line if statements, etc. Please fix them up.
Also DO NOT USE PROC! Please use the proper kernel interfaces if you
wish to dump loads of statistics to userspace (your own filesystem,
sysfs, debugfs (hint, hint, hint...)
Also, there are a lot more virtual fs in the kernel than you are
checking against in your "don't care about these files" test. You need
to have a comprehensive list if you want to get it correct.
thanks,
greg k-h
next prev parent reply other threads:[~2005-05-21 6:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-20 13:36 Reiner Sailer
2005-05-21 6:02 ` Greg KH [this message]
2005-05-22 19:37 ` 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-23 19:56 Reiner Sailer
2005-05-23 20:39 ` 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-24 13:45 Reiner Sailer
2005-05-24 18:47 ` Pavel Machek
2005-05-24 21:17 Reiner Sailer
2005-05-24 22:41 ` Pavel Machek
2005-05-25 15:00 Reiner Sailer
2005-05-25 15:06 ` Pavel Machek
2005-05-25 15:32 Reiner Sailer
2005-05-25 21:58 ` 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=20050521060236.GB24597@kroah.com \
--to=greg@kroah.com \
--cc=emilyr@us.ibm.com \
--cc=kylene@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@mail.wirex.com \
--cc=sailer@watson.ibm.com \
--cc=toml@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®