From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com
 [IPv6:2a00:1450:400c:c09::22a])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Wed,  3 Feb 2016 15:17:43 +0100 (CET)
Received: by mail-wm0-x22a.google.com with SMTP id l66so165775002wml.0
 for <dm-crypt@saout.de>; Wed, 03 Feb 2016 06:17:43 -0800 (PST)
References: <CAFnMBaRfu93jkgmZ_vLDChF7Uv-dCE6dNN6YkSxU3EFvn8iHtg@mail.gmail.com>
From: Milan Broz <gmazyland@gmail.com>
Message-ID: <56B20C05.7080307@gmail.com>
Date: Wed, 3 Feb 2016 15:17:41 +0100
MIME-Version: 1.0
In-Reply-To: <CAFnMBaRfu93jkgmZ_vLDChF7Uv-dCE6dNN6YkSxU3EFvn8iHtg@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] The future of disk encryption with LUKS2
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: ".. ink .." <mhogomchungu@gmail.com>, "dm-crypt@saout.de" <dm-crypt@saout.de>

On 02/03/2016 02:13 PM, .. ink .. wrote:
> I am curious about what problems luks1 current has and how luks2 is
> going to fix them but there
> seem to be no documentation about luks2 anywhere.

Yes, and it is just because I am completely out of time (I have planned
to send some information week ago :-)

> I just came across this link here[1] and i am very much interested in
> this presentation.Will it be
> recorded and posted online?

Yes, but this is just high level talk, do not expect anything useful for developers.
(It should be recorded.)

Anyway, please give me few weeks, I expect the design discussion will happen here
(I have a lot of to say why I am trying to do it this way.)
I just prefer to discuss existing proof-of-concept code that theoretic discussions.

For now, LUKS2 is experiment (partially proof-of-concept of some ideas
of configurable keyslots, partially as testbed for my university work
as implementing Argon 2 as PBKDF2 replacement etc).

(You already found one serious mistake in code, so do not use it yet :)

> Will any of the materials used in the presented posted online
> somewhere for the rest of us to see?

yes 

Milan

> 
> 
> [1] https://devconfcz2016.sched.org/event/5nsA/the-future-of-disk-encryption-with-luks2
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
>