From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <guilhem@fripost.org>
Received: from outgoing.fripost.org (giraff.fripost.org [193.234.15.44])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Fri, 23 Nov 2018 19:33:51 +0100 (CET)
Date: Fri, 23 Nov 2018 19:26:26 +0100
From: Guilhem Moulin <guilhem@fripost.org>
Message-ID: <20181123182626.GB10414@localhost.localdomain>
References: <20180727081626.GA29834@localhost.localdomain>
 <d349eeb9-4509-e188-4bb2-90854bcc9a69@gmail.com>
 <20180730204718.GA16752@localhost.localdomain>
 <20180731060030.GA15852@h-174-65.A328.priv.bahnhof.se>
 <20180731075342.GA25101@localhost.localdomain>
 <aa607562-adad-6aaa-1865-df1e43eea44a@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <aa607562-adad-6aaa-1865-df1e43eea44a@gmail.com>
Subject: Re: [dm-crypt] Debian installer formatting LUKS2 devices by default?
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <https://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <https://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: <https://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: Milan Broz <gmazyland@gmail.com>
Cc: dm-crypt@saout.de

Hi Milan,

On Fri, 23 Nov 2018 at 10:21:40 +0100, Milan Broz wrote:
> just an update to LUKS2 as a default:

Thanks for the update!  Was about to poke this thread :-)

> I had to postpone a plan to release 2.1 with LUKS2 as default format
> (to January/February 2019), and we will release very soon 2.0.6 with some=
 fixes
> of LUKS2 format validation that need to be in place before we switch the =
default.

I see, for Debian Buster another blocker right now is the fixed libblkid
=66rom util-linux 2.33, although I've been told it's likely to make it for
Buster (it's in experimental right now).

FWIW, the release dates for Buster are the following [0]:

    2019-01-12  Transition freeze
    2019-02-12  Soft freeze (no new packages, no re-entry, 10-day migration=
s)
    2019-03-12  Full freeze

So if 2.1 doesn't trigger a transition due to a SONAME bump, releasing
it in February gives enough time to ship it to Buster.  (Strictly
speaking the deadline is March 02, assuming no RC bug is filed at the
last minute.)  I guess I'll poke this thread in early February to see
where we stand.

Cheers,
--=20
Guilhem.

[0] https://release.debian.org/