All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinz Diehl <htd@fancy-poultry.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] dm-crypt Digest, Vol 27, Issue 2
Date: Thu, 1 Sep 2011 19:18:17 +0200	[thread overview]
Message-ID: <20110901171817.GA2230@fancy-poultry.org> (raw)
In-Reply-To: <6dr65wvu3k4wfdi27eheaskw.1314891247270@email.android.com>

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?

  reply	other threads:[~2011-09-01 17:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-01 15:58 [dm-crypt] dm-crypt Digest, Vol 27, Issue 2 Shardis
2011-09-01 17:18 ` Heinz Diehl [this message]
2011-09-01 17:36 ` Arno Wagner
  -- strict thread matches above, loose matches on Subject: below --
2011-09-01 18:22 Shardis
2011-09-01 18:36 ` Arno Wagner
     [not found] <mailman.6.1314877132.9282.dm-crypt@saout.de>
2011-09-01 13:30 ` Yaron Sheffer
2011-09-01 17:24   ` Arno Wagner

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=20110901171817.GA2230@fancy-poultry.org \
    --to=htd@fancy-poultry.org \
    --cc=dm-crypt@saout.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.