[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1275683155.2644.91.camel@localhost.localdomain>
Date: Fri, 04 Jun 2010 16:25:55 -0400
From: David Safford <safford@...son.ibm.com>
To: James Morris <jmorris@...ei.org>
Cc: Mimi Zohar <zohar@...ux.vnet.ibm.com>, Shaz <shazalive@...il.com>,
linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org,
Dave Hansen <dave@...ux.vnet.ibm.com>,
Arjan van de Ven <arjan@...radead.org>,
securityengineeringresearchgroup
<securityengineeringresearchgroup@...glegroups.com>
Subject: Re: [ProbableSpam] Re: [PATCH 00/14] EVM
On Fri, 2010-06-04 at 10:57 +1000, James Morris wrote:
> On Tue, 1 Jun 2010, Mimi Zohar wrote:
>
> > SELinux, Smack, Capabilities, and IMA all use extended attributes. The
> > purpose of EVM is to detect offline tampering of these security extended
> > attributes.
>
> One issue mentioned to me off-list is that if EVM is only protecting
> against offline attacks, why not just encrypt the entire volume ?
>
> This would provide confidentiality and integrity protection for all data
> and metadata, rather than just integrity for xattr metadata.
Software whole disk encryption is slower, and doesn't really provide
integrity protection. While there are encryption modes, such as
IAPM (Integrity Aware Parallelizable Mode) which can provide both
confidentially and integrity guarantees, they are hard to use for
random access devices. An example attack is replaying previously
valid encrypted blocks, to revert to a previous version with a known
vulnerabiity. With EVM, these attacks can be defeated
efficiently with directory level binding. (This is on our TODO list).
With encryption in the hard disk, the performance is less of an issue,
but the integrity problem is still there. Plus, most systems don't
have the encrypting drives, and need a software solution.
dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists