From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 24 15:19:30 2008 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7B26316A402 for ; Sun, 24 Feb 2008 15:19:30 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id 2D77413C457 for ; Sun, 24 Feb 2008 15:19:29 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from working (c-71-60-127-199.hsd1.pa.comcast.net [71.60.127.199]) (AUTH: LOGIN wmoran, SSL: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Sun, 24 Feb 2008 10:09:25 -0500 id 0005641D.47C188A5.00012960 Date: Sun, 24 Feb 2008 10:09:24 -0500 From: Bill Moran To: "Igor Mozolevsky" Message-Id: <20080224100924.c8e08776.wmoran@collaborativefusion.com> In-Reply-To: References: <47C06E1F.5020308@thedarkside.nl> <760775.85636.qm@web50306.mail.re2.yahoo.com> <20080223203316.GC38485@lor.one-eyed-alien.net> Organization: Collaborative Fusion Inc. X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: Security Flaw in Popular Disk Encryption Technologies X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Feb 2008 15:19:30 -0000 "Igor Mozolevsky" wrote: > > On 23/02/2008, Brooks Davis wrote: > > > > > You should actually read the paper. :) They successfully defeat both > > of these type of protections by using canned air to chill the ram and > > transplanting it into another machine. > > Easy to get around this attack - store the key on a usb > stick/cd/whatever and every time the OS needs to access the encrypted > date the key should be read, data decrypted, then key wiped from the > memory; or have the daemon erase the key from memory every T minutes > and re-acquire the key at next access attempt... This is only effective if the sensitive data is infrequently accessed. If the unit is asleep, then software isn't running and it's not possible to kick of a timer to clear the memory, so it doesn't even start to solve that problem. > Or you could carry something that emits a huge EMI pulse to destroy > the data on the disk... Or laptop vendors could make "secure" laptops that always lose memory on shutdown. There are a number of vendors out there who make so-called "secure" laptops (hell, even the new Lenovos brag of security with their fingerprint readers). I wonder if they tested different hardware ... i.e. if some laptops are more vulnerable than others, or even some laptop hardware is _not_ vulnerable at all? I'm also disappointed that they took the tack of calling this a "software" problem and investigating so many different softwares. They should have identified it as a limitation of the hardware and tested different hardware. -- Bill Moran Collaborative Fusion Inc. wmoran@collaborativefusion.com Phone: 412-422-3463x4023