DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: mgreger@cinci.rr.com
To: "'dm-crypt@saout.de'" <dm-crypt@saout.de>
Subject: Re: [dm-crypt] Two questions
Date: Wed, 13 Nov 2019 18:42:55 +0000	[thread overview]
Message-ID: <14224469d70c38f8c34baf4e2f750d4089993ab6@webmail> (raw)

[-- Attachment #1: Type: text/plain, Size: 772 bytes --]



	From Michael Kjörling:

	> Yes; it implies that the two volumes are encrypted using the same
master key (as well as being accessible using the same set of
passphrases), _and_ it makes it obvious that this is the case.

	(Assume any detached header is absent)

	 Obvious by inspecting the raw encrypted drives? My concern is
salt/iv reuse for same sector #'s on multiple drives leading to
information leakage.

	For example let's say two encrypted drives were mirrored. Using the
same master key would make it obvious they are mirrored, but no
additional information is leaked (other than that they are in fact
copies of each other). But more complex scenarios exist: RAID, LVM2
headers, etc. Those other scenarios are the ones I am curious about.


[-- Attachment #2: Type: text/html, Size: 955 bytes --]

             reply	other threads:[~2019-11-13 18:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-13 18:42 mgreger [this message]
2019-11-13 23:16 ` [dm-crypt] Two questions Arno Wagner
  -- strict thread matches above, loose matches on Subject: below --
2019-11-14  2:45 mgreger
2019-11-14  2:43 mgreger
2019-11-13 15:15 mgreger
2019-11-13 18:07 ` Michael Kjörling
2019-11-14  9:15 ` Ondrej Kozina
2019-11-15 10:00 ` Milan Broz

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=14224469d70c38f8c34baf4e2f750d4089993ab6@webmail \
    --to=mgreger@cinci.rr.com \
    --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