All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>, dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS GPT GUID
Date: Tue, 28 Jan 2014 17:58:11 +0100	[thread overview]
Message-ID: <52E7E1A3.3010600@gmail.com> (raw)
In-Reply-To: <1390857135.5258.30.camel@heisenberg.scientia.net>

On 01/27/2014 10:12 PM, Christoph Anton Mitterer wrote:
> On Mon, 2014-01-27 at 21:41 +0100, Milan Broz wrote:
>> "Encrypted disk partition (LUKS, dm-crypt, TrueCrypt, loop-AES or similar)"
>> With GUID generated (without doubt by properly seeded Christoph's RNG ;-)
>> ca7d7ccb-63ed-4c53-861c-1742536059cc
> 
> I think at most we should say:
> LUKS or rather even 
> LUKS = ca7d7ccb-63ed-4c53-861c-1742536059cc
> dm-crypt = 7ffec5c9-2d00-49b7-8941-3ea10a5586b7
> ... but especially not mix TC and loop-AES together, since dm-crypt is
> not the upstream for them...

My idea was just to use one generic encrypted partition marking, whatever
format it is...

But really, who cares? :) If you want, send it to the "upstream".

Milan

  reply	other threads:[~2014-01-28 16:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-26  1:40 [dm-crypt] LUKS GPT GUID Pali Rohár
2014-01-26  9:24 ` Milan Broz
2014-01-26 10:17   ` Pali Rohár
2014-01-26 16:02     ` Rod Smith
2014-01-26 15:55   ` Christoph Anton Mitterer
2014-01-27  9:53   ` Karel Zak
2014-01-27 10:05     ` Pali Rohár
2014-01-27 10:40       ` Karel Zak
2014-01-27 10:49         ` Pali Rohár
2014-01-27 11:47         ` Sven Eschenberg
2014-01-27 15:25     ` Christoph Anton Mitterer
2014-01-27 20:41       ` Milan Broz
2014-01-27 21:12         ` Christoph Anton Mitterer
2014-01-28 16:58           ` Milan Broz [this message]
2014-01-29 13:47             ` Christoph Anton Mitterer
2014-01-28  0:04         ` Arno Wagner
2014-01-26 13:18 ` Arno Wagner
2014-01-31 20:56 ` Pali Rohár
2014-01-31 21:32   ` Christoph Anton Mitterer

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=52E7E1A3.3010600@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=calestyo@scientia.net \
    --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.