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, 25 Jan 2019 14:54:42 +0100	[thread overview]
Message-ID: <20190125135442.GA24862@fripost.org> (raw)
In-Reply-To: <aa607562-adad-6aaa-1865-df1e43eea44a@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 649 bytes --]

Hi Milan,

On Fri, 23 Nov 2018 at 10:21:40 +0100, Milan Broz wrote:
> 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.

With the full Freeze approaching we (Debian package maintainers) are
often asked about LUKS2 status; so I wonder if the plan is still to
release 2.1 before the end of February? :-)

Thanks,
cheers,
-- 
Guilhem.

PS. Also, if you or another cryptsetup upstream will be back to FOSDEM
    this year, I'd love to say hi! ;-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2019-01-25 14:02 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
2018-11-23 18:46             ` Milan Broz
2019-01-25 13:54           ` Guilhem Moulin [this message]
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=20190125135442.GA24862@fripost.org \
    --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.