From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=8ovm=OL=saout.de=dm-crypt-bounces@kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
X-Spam-Level: **
X-Spam-Status: No, score=2.5 required=3.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,
	HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI,SPF_HELO_NONE,
	SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0
Received: from mail.kernel.org (mail.kernel.org [198.145.29.99])
	by smtp.lore.kernel.org (Postfix) with ESMTP id B5F9FC433F5
	for <dm-crypt@archiver.kernel.org>; Tue, 21 Sep 2021 12:56:15 +0000 (UTC)
Received: from mail.server123.net (mail.server123.net [78.46.64.186])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by mail.kernel.org (Postfix) with ESMTPS id 3EF5161166
	for <dm-crypt@archiver.kernel.org>; Tue, 21 Sep 2021 12:56:15 +0000 (UTC)
DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 3EF5161166
Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com
Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=saout.de
X-Virus-Scanned: amavisd-new at saout.de
Authentication-Results: mail.server123.net (amavisd-new);
	dkim=pass (2048-bit key) header.d=gmail.com
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2a00:1450:4864:20::435; helo=mail-wr1-x435.google.com; envelope-from=jtmoree@gmail.com; receiver=<UNKNOWN> 
Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435])
	(using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
	(No client certificate requested)
	by mail.server123.net (Postfix) with ESMTPS
	for <dm-crypt@saout.de>; Tue, 21 Sep 2021 14:53:33 +0200 (CEST)
Received: by mail-wr1-x435.google.com with SMTP id d6so38673662wrc.11
        for <dm-crypt@saout.de>; Tue, 21 Sep 2021 05:53:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20210112;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to
         :cc;
        bh=UBnnYLGqifIXAnjmi7Nyb6h0IygDhjlCvwwyiNt/pj4=;
        b=N95Uxa8ci+r52vEmLE+2FAkEIrVV/OAhlj/YVEoky7j1VgEQtnNx2oHV9pzyvK5fu3
         JnRtLFKLwMJUNuBFLv5/MJBZa04x0sFIO0OhDjfRecvDqT9yjoL8WhYzIZthV6WVhkIB
         XG5V6UN79JJhkq03qvkVzeuOz8tiAZQ0dVQ3vBji+DTruLYEJkdPd6e2hBO1ysECKs3W
         /CX9aWyrj4OXzJsODxBkx1t8S7UDOT189m9Zb09Jaq8O3aK3h9/uj2soG2Bxo3YATpK3
         +jR3dfIYUDPZOntpH1rxYWS7N011aUpbQ9Jjl8bSA7K37f5GpvjV3QX4BSZ8zJm6oZos
         wovQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20210112;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:cc;
        bh=UBnnYLGqifIXAnjmi7Nyb6h0IygDhjlCvwwyiNt/pj4=;
        b=pRWT+Hfjr1XfJrAEQBrxI7FsmbmQwPNAWcWF9G8LsG0xozr3ByIq7GMh4ajnWuPF4a
         7Yhx2Z+I+aZ9t1NXZatTrtQKxc3mu3izCS+gs8nv8fLIYzI1U6d1ocF0V+ghPdpkzKRI
         ScPSia8tBYTQreLUexmBDyh+cE255+LxqTxgmFMtygpWunMh8yMdh4XfcQ/XW123zzFz
         0cluVKbw2ignSpQlXF/0Bnyu9SRYoHCx5xhiKuwrLW5/I+EpAQFczr6xF5lYpNKTfI1p
         CoXdsbN1Isvn5O/6zlR5uuv8ztfyJdqRXATkdckN4Prjdg1U4rnG1ErtjmOm3+Prh5sQ
         ngeQ==
X-Gm-Message-State: AOAM531DKUHnAj7dzBJnFEBImH0MHL4w1gXPfaqmbkNcSGR+wrCHwsk9
	5AXpIcjzF8q0u1nQYUm3QO2NqqVJFpp1OhSoS6k=
X-Google-Smtp-Source: ABdhPJzMGcrbB9X5prXI9bbO5P55YXsuEUUV2DiMqHphCtyypDMltONISgCmYCb0JynpROIxfV6cIKyWZrSsLS6xX3Y=
X-Received: by 2002:a05:6000:1562:: with SMTP id 2mr31768161wrz.36.1632228812225;
 Tue, 21 Sep 2021 05:53:32 -0700 (PDT)
MIME-Version: 1.0
References: <c3cb2dfa-14c7-f6c7-c3b9-a8664b9168db@btinternet.com> <66a59a26-726f-9439-fc9c-85018d619cc8@redhat.com>
In-Reply-To: <66a59a26-726f-9439-fc9c-85018d619cc8@redhat.com>
From: Jeremiah Moree <jtmoree@gmail.com>
Date: Tue, 21 Sep 2021 05:53:21 -0700
Message-ID: <CAAz2dUgCMDubOeHmX2LTiTrbs494fKtOiiQju5o6exTE_qWkSQ@mail.gmail.com>
To: Ondrej Kozina <okozina@redhat.com>
Message-ID-Hash: ULTIW6KDOJRF2WPQFRTQPGL3XSREFDRO
X-Message-ID-Hash: ULTIW6KDOJRF2WPQFRTQPGL3XSREFDRO
X-MailFrom: jtmoree@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dm-crypt.saout.de-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header
CC: dmcrypt <dm-crypt@saout.de>, Stephen Feyrer <stephen.feyrer@btinternet.com>
X-Mailman-Version: 3.3.2
Precedence: list
Subject: [dm-crypt] Re: cryptsetup - 2FA feature request
List-Id: <dm-crypt.saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Post: <mailto:dm-crypt@saout.de>
List-Subscribe: <mailto:dm-crypt-join@saout.de>
List-Unsubscribe: <mailto:dm-crypt-leave@saout.de>
Content-Type: multipart/mixed; boundary="===============2517302941098827771=="

--===============2517302941098827771==
Content-Type: multipart/alternative; boundary="0000000000008b7fe705cc80e283"

--0000000000008b7fe705cc80e283
Content-Type: text/plain; charset="UTF-8"

>
> In before activation by passphrase (interactive query) we try to
> activate device using any available token handler in the system
> (crypt_activate_by_token & crypt_activate_by_token_pin library API).
> Only when no appropriate LUKS2 token can be used to unlock the device we
> fall back to passphrase based activation.
>

I was looking for detailed documentation on token handling plugins but not
finding it.  Am I missing it?   Is it in the man page or the luks2 pdf or
the wiki or the readme? or somewhere else?

In lieu of the docs I plan to start some code and communicate with the
mailing list but given the problems with the mailing list lately I am
waiting.  (I keep getting kicked off--both email addresses).

-- 
JT

--0000000000008b7fe705cc80e283
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex">In before activation by passphrase (interactive query) w=
e try to <br>
activate device using any available token handler in the system <br>
(crypt_activate_by_token &amp; crypt_activate_by_token_pin library API). <b=
r>
Only when no appropriate LUKS2 token can be used to unlock the device we <b=
r>
fall back to passphrase based activation.<br></blockquote><div><br></div><d=
iv>I was looking for detailed documentation on token handling plugins but n=
ot finding it.=C2=A0 Am I missing it?=C2=A0 =C2=A0Is it in the man page or =
the luks2 pdf or the wiki or the readme? or somewhere else?=C2=A0=C2=A0</di=
v><div><br></div><div>In lieu=C2=A0of the docs I plan to start some code an=
d communicate with the mailing list but given=C2=A0the problems with the ma=
iling list lately I am waiting.=C2=A0 (I keep getting kicked off--both emai=
l addresses).</div><div><br></div></div>-- <br><div dir=3D"ltr" class=3D"gm=
ail_signature">JT</div></div>

--0000000000008b7fe705cc80e283--

--===============2517302941098827771==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
dm-crypt mailing list -- dm-crypt@saout.de
To unsubscribe send an email to dm-crypt-leave@saout.de

--===============2517302941098827771==--