From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <htd@fancy-poultry.org>
Received: from mail.saout.de ([127.0.0.1])
 by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 03UWZHjJDJ57 for <dm-crypt@saout.de>;
 Mon, 16 Apr 2012 21:54:10 +0200 (CEST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Mon, 16 Apr 2012 21:54:09 +0200 (CEST)
Date: Mon, 16 Apr 2012 21:53:32 +0200
From: Heinz Diehl <htd@fancy-poultry.org>
Message-ID: <20120416195332.GA2887@fancy-poultry.org>
References: <d5178ad7d817b412fa60133d721b41b5.squirrel@ssl.verfeiert.org>
 <1334536105.71826.YahooMailClassic@web171306.mail.ir2.yahoo.com>
 <20120416024321.GB22656@tansi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20120416024321.GB22656@tansi.org>
Subject: Re: [dm-crypt] simple ideas addressing ssd TRIM security concern
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

On 16.04.2012, Arno Wagner wrote: 

> > Weighing out really is the most difficult part when you have no tangible
> > data: how much is it difficult to break a TRIMed and crypted device?
 
> It is not difficult. It is impossible.

If this is true, then why not use it and end of story?