From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>
Cc: Martin Steigerwald <martin@lichtvoll.de>, linux-btrfs@vger.kernel.org
Subject: Re: send/receive for encrypted backup purposes
Date: Fri, 8 Jan 2016 10:04:33 -0500 [thread overview]
Message-ID: <568FD001.3030204@gmail.com> (raw)
In-Reply-To: <1452264547.6727.23.camel@scientia.net>
On 2016-01-08 09:49, Christoph Anton Mitterer wrote:
> On Fri, 2016-01-08 at 09:40 -0500, Austin S. Hemmelgarn wrote:
>> That said, if you're using forced compression
>> on
>> the source FS, that may weaken things a bit.
> The compression oracle it typically only then a problem, when the
> attacker can control the encrypted data.
> So that would depend mostly on his content...
>
> But better safe than sorry... compression should usually be avoided
> with crypto.
Oh, definitely. And that goes double for cases where the compression
algorithm is known in advance by the attacker (because if you pay
attention, a lot of compression algorithms produce certain patterns,
which makes breaking things a lot easier, even if you don't control part
of the plaintext).
next prev parent reply other threads:[~2016-01-08 15:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 13:44 send/receive for encrypted backup purposes Martin Steigerwald
2016-01-08 14:00 ` Christoph Anton Mitterer
2016-01-08 14:02 ` Swâmi Petaramesh
2016-01-08 14:07 ` Christoph Anton Mitterer
2016-01-08 14:40 ` Austin S. Hemmelgarn
2016-01-08 14:49 ` Christoph Anton Mitterer
2016-01-08 15:04 ` Austin S. Hemmelgarn [this message]
2016-01-08 15:01 ` Austin S. Hemmelgarn
2016-01-09 19:05 ` Christoph Biedl
2016-01-11 12:50 ` Austin S. Hemmelgarn
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=568FD001.3030204@gmail.com \
--to=ahferroin7@gmail.com \
--cc=calestyo@scientia.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=martin@lichtvoll.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).