All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mitch Harder <mitch.harder@sabayonlinux.org>
To: merc1984@f-m.fm
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Encryption
Date: Wed, 12 Dec 2012 12:31:41 -0600	[thread overview]
Message-ID: <CAKcLGm8gH09DgouymqLL1MKi49kZvHx36M=X1yk5gCWD+iOhQQ@mail.gmail.com> (raw)
In-Reply-To: <1355332339.17999.140661165184497.5BC0F72B@webmail.messagingengine.com>

On Wed, Dec 12, 2012 at 11:12 AM,  <merc1984@f-m.fm> wrote:
>
> So there is no way to have filesystem encryption, while keeping
> snapshots?
>
>

I run btrfs on top of LUKS encryption on my laptop.  You should be
able to do the same.

You could then run rsync through ssh.  However, rsync will have no
knowledge of any blocks shared under subvolume snapshots.

Btrfs does not yet have internal encryption.

  reply	other threads:[~2012-12-12 18:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-07 16:16 merc1984
2012-12-12 17:12 ` Encryption merc1984
2012-12-12 18:31   ` Mitch Harder [this message]
2012-12-12 18:38     ` Encryption merc1984
2012-12-12 18:48       ` Encryption cwillu
2012-12-12 20:06         ` Encryption merc1984
2012-12-12 20:22           ` Encryption cwillu
2012-12-13  9:17           ` Encryption Sander
2012-12-13 17:23             ` Encryption merc1984
2012-12-13 22:39               ` Encryption Hugo Mills
  -- strict thread matches above, loose matches on Subject: below --
2015-02-16 17:19 encryption Henry Noack
2015-02-18 11:03 ` encryption Stefan Hajnoczi
2015-02-18 11:58   ` encryption Markus Armbruster
2011-01-20 15:05 Encryption Carl Cook
2011-01-20 15:14 ` Encryption Hugo Mills
2011-01-20 16:10 ` Encryption Josef Bacik
2003-03-22 23:22 Encryption Pierre Abbat
2003-03-22 23:29 ` Encryption Yury Umanets
2003-03-24 20:37   ` Encryption Hans Reiser
2003-03-25 19:18     ` Encryption Edward Shushkin

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='CAKcLGm8gH09DgouymqLL1MKi49kZvHx36M=X1yk5gCWD+iOhQQ@mail.gmail.com' \
    --to=mitch.harder@sabayonlinux.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=merc1984@f-m.fm \
    /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.