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 barpJ3ISB-wA for <dm-crypt@saout.de>;
 Thu,  1 Sep 2011 19:18:02 +0200 (CEST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Thu,  1 Sep 2011 19:18:02 +0200 (CEST)
Date: Thu, 1 Sep 2011 19:18:17 +0200
From: Heinz Diehl <htd@fancy-poultry.org>
Message-ID: <20110901171817.GA2230@fancy-poultry.org>
References: <6dr65wvu3k4wfdi27eheaskw.1314891247270@email.android.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6dr65wvu3k4wfdi27eheaskw.1314891247270@email.android.com>
Subject: Re: [dm-crypt] dm-crypt Digest, Vol 27, Issue 2
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 01.09.2011, Shardis wrote: 

> Personally, I tend to find that the only sane technical reason not to encrypt anything considered 
> sensitive these days is CPU cycle cost.

"Security is essentially a trade-off" (B. Schneier). If the data is worth the encryption, you'll have to live with cpu overhead.
If it's not: why do you want to have it encrypted, then?

> Why would you ever NOT want to encrypt in house?

Because the data isn't worth it?