All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] advice on encrypted snapshots
Date: Sun, 1 Nov 2009 22:39:59 +0100	[thread overview]
Message-ID: <20091101213958.GA32758@tansi.org> (raw)
In-Reply-To: <20091101080647.GA2090@maude.comedia.it>

On Sun, Nov 01, 2009 at 09:06:48AM +0100, Luca Berra wrote:
> On Sun, Nov 01, 2009 at 03:05:31AM +0100, Arno Wagner wrote:
>> One pice of meta-advice may be appropriate:
>>
>> Try for simplicity. If you feel your solution is getting
>> too complex to understand it in one go, try very hard to
>> find a simpler one. Complex solutions are not only a lot
>> more likely to fail, the chances for them to be secure
>> are a lot worse.
> The solution i proposed at the beginning, encrypt the pv, was the
> simplest and more secure one, it also prevented any possible leak.
> Alas it does not work in the op environment, so we have to find a better
> one.
> Here comes solution two, snapshot the lv, it is still quite simple,
> there is the possibility of some information leak, but i don't really
> believe the cow table and some modified sector are enough material for
> cryptanalysis.
> But solution two fails, I can luksOpen either the original lv or the
> snapshot, but not both at the same time. I have no idea if this is a
> intended, a bug, or if i am overlooking something obvious.
>
>> Incidentially, the ooriginal question was about file backups, not 
>> snapshots. If you want a snapshot and
>> can afford to umount the device, just use dd.
> incidentally it was about snapshots, but your advice about dd makes me
> realize you have no idea what a snapshot is.

Actually I do know what a snapshot is. You are thinking of a 
more complex operation it seems, namely snapshot taking and 
then conventional, file based backup of the snapshot. 

No reason why an encryption layer should add problems. Of 
course you need to snapshot the encrypted volume,
and you may want to sync or better umount the volume during
snapshot taking. 

Arno
-- 
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name 
GnuPG:  ID: 1E25338F  FP: 0C30 5782 9D93 F785 E79C  0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier 

  reply	other threads:[~2009-11-01 21:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-30 20:05 [dm-crypt] advice on encrypted snapshots Ross Boylan
2009-10-31  5:34 ` Arno Wagner
2009-10-31  7:13 ` Heinz Diehl
2009-10-31  8:12 ` Luca Berra
2009-10-31 18:03   ` Ross Boylan
2009-10-31 23:39     ` Luca Berra
2009-11-01  2:05       ` Arno Wagner
2009-11-01  3:29         ` Ross Boylan
2009-11-01  8:06         ` Luca Berra
2009-11-01 21:39           ` Arno Wagner [this message]
2009-11-04  0:43     ` [dm-crypt] advice on encrypted snapshots [solved] Ross Boylan

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=20091101213958.GA32758@tansi.org \
    --to=arno@wagner.name \
    --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.