From: "Michael Kjörling" <michael@kjorling.se>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] How to compress LUKS v2 header?
Date: Thu, 26 Dec 2019 21:38:40 +0000 [thread overview]
Message-ID: <4znhwwdjmp4rtw4jmrtp93xg@localhost> (raw)
In-Reply-To: <fbd7b3b7e45a48d7896cb3b644fd86bb@br.ibm.com>
On 26 Dec 2019 20:20 +0000, from jfaracco@br.ibm.com (Julio Cesar Faracco - jfaracco@br.ibm.com):
> I'm using `cryptsetup luksHeaderBackup /dev/sda2 --header-backup-file /tmp/backup.header`
> I used ZIP and GZIP, but I got 0% of reduction of `backup.header`. :-(
> Do you have any suggestions of what algorithm should be used to
> compress this type of file?
Why are you trying to compress the header backup in the first place?
As a general rule, encrypted data (such as the parts of the LUKS
header that aren't already random by design) does not compress well;
if data that has been encrypted can be compressed to any notable
degree, that usually means the encryption is somehow flawed, because
it's leaving patterns in the encrypted data. Properly encrypted data
should look completely random, which means that there's very little,
if anything, for compression utilities to find reducible patterns in.
--
Michael Kjörling • https://michael.kjorling.se • michael@kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”
next prev parent reply other threads:[~2019-12-26 21:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 20:20 [dm-crypt] How to compress LUKS v2 header? Julio Cesar Faracco - jfaracco@br.ibm.com
2019-12-26 21:38 ` Michael Kjörling [this message]
2019-12-27 9:30 ` Arno Wagner
2019-12-27 13:37 ` Julio Cesar Faracco - jfaracco@br.ibm.com
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=4znhwwdjmp4rtw4jmrtp93xg@localhost \
--to=michael@kjorling.se \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox