From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <moreejt@yahoo.com>
Received: from sonic306-20.consmr.mail.gq1.yahoo.com
 (sonic306-20.consmr.mail.gq1.yahoo.com [98.137.68.83])
 (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>; Fri,  3 Apr 2020 22:53:09 +0200 (CEST)
Date: Fri, 3 Apr 2020 20:53:03 +0000 (UTC)
From: =?UTF-8?Q?JT_Mor=C3=A9e?= <moreejt@yahoo.com>
Message-ID: <2008628359.200095.1585947183040@mail.yahoo.com>
In-Reply-To: <c670fbd3-5da3-dcc8-3b8f-831a47c4a524@redhat.com>
References: <5602805.1319309.1585599459612.ref@mail.yahoo.com>
 <5602805.1319309.1585599459612@mail.yahoo.com>
 <8e692b82-04cc-693c-08e7-cb6524916c23@redhat.com>
 <d644f810-3897-00eb-139a-5b8856686549@redhat.com>
 <1105535389.1850547.1585667111461@mail.yahoo.com>
 <c670fbd3-5da3-dcc8-3b8f-831a47c4a524@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [dm-crypt] unbound keys
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: Dm-crypt <dm-crypt@saout.de>


> But if you're interested in automatic unlocking via tokens, I'd=20
recommend to wait for cryptsetup-2.4.0 RC0 announce. We're working on=20
adding support for dynamically loadable plugins and that's probably what=20
you'd want wait for.

That sounds good.=C2=A0 I will wait for 2.4.0 before working on this again.=
=C2=A0 I have a manually working solution for my current needs.

Can you give a rough ETA on 2.4.0 RC?=C2=A0 3 months, 1 year?=C2=A0 just cu=
rious

JT