All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: Ross Boylan <ross@biostat.ucsf.edu>
Subject: Re: [dm-crypt] advice on encrypted snapshots
Date: Sat, 31 Oct 2009 06:34:18 +0100	[thread overview]
Message-ID: <20091031053418.GA11664@tansi.org> (raw)
In-Reply-To: <1256933154.21609.14.camel@markov.biostat.ucsf.edu>

On Fri, Oct 30, 2009 at 01:05:54PM -0700, Ross Boylan wrote:
> Does anyone have any advice about how to snapshot an encrypted volume so
> that the snapshot won't leak information?
> 
> This is for a backup; I'm aware that the backup system involves
> additional security challenges. I want to do a file-based, rather than
> disk-image, backup.

Hmm. Use "tar -f" to do an archive file and encrypt that image
on-the-fly with pgp/GnuPG. This way you can write the backup 
directly to unencrypted space.

The command could look as follows:

  tar cf - <path_to_data> | gpg -e -r <key owner> -o backup.tar.gpg -

Compression by tar is a bit redundant, as PGP/GnuPG also compress, 
but YMMV. The "f -" part to tar causes it to write to STDOUT
and the trailing "-" causes gpg to read from STDIN. In that
case gpg needs the output file name via "-o".

The above requires you to have a key for <key owner> set up
and the security of the backup then depends on the security
of that key. Note that you do not need the passphrase for 
encryption, only later for decyption. If you wan to use a
passhprase for the backup instead (no public-key crypto
involved), use the -c option to gpg. You can supply the 
passphrase in several ways, see the --passphrase-<something>
options.

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-10-31 14:57 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 [this message]
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
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=20091031053418.GA11664@tansi.org \
    --to=arno@wagner.name \
    --cc=ross@biostat.ucsf.edu \
    /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.