util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@ubuntu.com>
To: "Dale R. Worley" <worley@alum.mit.edu>,
	770211@bugs.debian.org, Drake Wilson <drake@dasyatidae.net>
Cc: util-linux@vger.kernel.org
Subject: Re: Bug#770211: LUKS partition types, redux
Date: Thu, 20 Nov 2014 11:43:02 -0500	[thread overview]
Message-ID: <546E1A16.6050102@ubuntu.com> (raw)
In-Reply-To: <201411192224.sAJMOhTi010782@hobgoblin.ariadne.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/19/2014 5:24 PM, Dale R. Worley wrote:
> This raises the related question of whether there should be codes
> to identify the partition type inside the LUKS partition.  That is,
> the partition table code identifies the partition as a LUKS
> partition, but once one has supplied the keys for LUKS encryption,
> is there any way to tell the type of the encrypted partition
> without testing for magic numbers (using "file" or the like)?

Linux doesn't pay any attention to partition type codes anyhow and
just uses blkid to identify the contents.

> I suppose there aren't enough type codes in MBR to allow
> separately identifying "ext4 inside LUKS", but with GPT it would be
> possible, and even could be done systematically.  E.g., if the UUID
> for a partition type is XXX, then the partition type for that type
> inside of LUKS is MD5("LUKS" XXX)...
> 
> Then again, perhaps you would not want to reveal the type of the 
> encrypted partition.

That too.



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)

iQEcBAEBAgAGBQJUbhoWAAoJEI5FoCIzSKrwfZAH/AnTDFG8Nes4Sa+cKebZs9D/
Atf7SrWYQFy++p0o0sNKcSIrdjHghIGEzq8oTZ5pBgnEfu94/uTATUSGSFum7bqL
3ZYPgKNGi7SOj/Oc03p+Tzadjk01gpHUQMcj8jcHJUbrJheLCssPyB558vA5Vqrz
D8bLbOz9JmoDQ+zpWrachKv3+7XAfh0ri54tKsEmNFKN3LOhrxyoVfIGIJf+MFQK
kssPT/ZKD3W/PEBTaI/pcwaCo1+vdR2JYiy4ODBQy7LMfvvw97N3aZEKgRGgLudF
NWApQR7AZLxjD2YllE0NI2NBeq4/8DgLicwnnJSqdHvKFKlbwC0Iq5wIugNjSds=
=s8LS
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2014-11-20 16:43 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-19 20:59 LUKS partition types, redux Drake Wilson
2014-11-19 22:24 ` Dale R. Worley
2014-11-19 22:37   ` Drake Wilson
2014-11-20 21:33     ` Dale R. Worley
2014-11-21  7:47       ` Milan Broz
2014-11-21  7:54         ` LUKS partition types, redux (wandering into the weeds) Drake Wilson
2014-11-20 16:43   ` Phillip Susi [this message]
2014-11-24  4:45     ` Bug#770211: LUKS partition types, redux Drake Wilson
2014-11-24 14:33       ` Phillip Susi
2014-11-24 14:37         ` Drake Wilson
2014-11-24 14:45           ` Phillip Susi
2014-11-24 14:48           ` Drake Wilson
2014-11-24 14:58             ` Phillip Susi
2014-11-24 15:04               ` Drake Wilson
2014-11-24 15:09                 ` Phillip Susi
2014-11-24 16:10               ` Karel Zak
2014-11-24 16:27                 ` Phillip Susi
2014-11-25 15:18                 ` Dale R. Worley
2014-11-24 11:37 ` Karel Zak
2014-11-24 12:09   ` Drake Wilson
2014-11-24 14:42   ` Phillip Susi
2014-11-24 15:46     ` Karel Zak
2014-11-24 19:56       ` Bruce Dubbs
2014-11-25 11:26         ` Karel Zak
2014-11-25 15:36           ` Bruce Dubbs
2014-11-25 15:20       ` Dale R. Worley
2014-11-24 15:48     ` Dale R. Worley

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=546E1A16.6050102@ubuntu.com \
    --to=psusi@ubuntu.com \
    --cc=770211@bugs.debian.org \
    --cc=drake@dasyatidae.net \
    --cc=util-linux@vger.kernel.org \
    --cc=worley@alum.mit.edu \
    /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).