All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guilhem Moulin <guilhem@fripost.org>
To: Milan Broz <gmazyland@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Debian installer formatting LUKS2 devices by default?
Date: Fri, 23 Nov 2018 19:26:26 +0100	[thread overview]
Message-ID: <20181123182626.GB10414@localhost.localdomain> (raw)
In-Reply-To: <aa607562-adad-6aaa-1865-df1e43eea44a@gmail.com>

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
from 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 migrations)
    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,
-- 
Guilhem.

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

  reply	other threads:[~2018-11-23 18:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-27  8:16 [dm-crypt] Debian installer formatting LUKS2 devices by default? Guilhem Moulin
2018-07-30 10:51 ` Milan Broz
2018-07-30 20:47   ` Guilhem Moulin
2018-07-31  6:00     ` Michael Kjörling
2018-07-31  7:53       ` Guilhem Moulin
2018-11-23  9:21         ` Milan Broz
2018-11-23 18:26           ` Guilhem Moulin [this message]
2018-11-23 18:46             ` Milan Broz
2019-01-25 13:54           ` Guilhem Moulin
2019-01-25 14:31             ` Milan Broz
2019-01-25 15:05               ` Guilhem Moulin
2019-02-05 15:29               ` Milan Broz
2018-07-31  8:56     ` 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=20181123182626.GB10414@localhost.localdomain \
    --to=guilhem@fripost.org \
    --cc=dm-crypt@saout.de \
    --cc=gmazyland@gmail.com \
    /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.