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] How to compress LUKS v2 header?
Date: Fri, 27 Dec 2019 10:30:51 +0100	[thread overview]
Message-ID: <20191227093050.GA5876@tansi.org> (raw)
In-Reply-To: <fbd7b3b7e45a48d7896cb3b644fd86bb@br.ibm.com>

Hi,

compressing the anti-forensic stripes would require breaking some 
pretty impressive crypto. In short, for all practical purposes,
compression is impossible.

Regards,
Arno

On Thu, Dec 26, 2019 at 21:20:44 CET, Julio Cesar Faracco - jfaracco@br.ibm.com wrote:
> Hi all,
> 
> I'm trying to compress a LUKS v2 header file, but I'm not seeing any
> sensible reduction.
> 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?
> 
> Thanks!
> 
> --     
> Julio  Cesar Faracco
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> https://www.saout.de/mailman/listinfo/dm-crypt

-- 
Arno Wagner,     Dr. sc. techn., Dipl. Inform.,    Email: arno@wagner.name
GnuPG: ID: CB5D9718  FP: 12D6 C03B 1B30 33BB 13CF  B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato

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

  parent reply	other threads:[~2019-12-27  9:30 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
2019-12-27  9:30 ` Arno Wagner [this message]
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=20191227093050.GA5876@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.