IETF Logo Mail Archive

Re: [Crypto-panel] Request for review: CPace

"Stanislav V. Smyshlyaev" <smyshsv@gmail.com> Wed, 11 October 2023 08:56 UTC

Return-Path: <smyshsv@gmail.com>
X-Original-To: crypto-panel@ietfa.amsl.com
Delivered-To: crypto-panel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 358C3C15108F for <crypto-panel@ietfa.amsl.com>; Wed, 11 Oct 2023 01:56:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TPXKxJhXmsZK for <crypto-panel@ietfa.amsl.com>; Wed, 11 Oct 2023 01:56:25 -0700 (PDT)
Received: from mail-yw1-x1136.google.com (mail-yw1-x1136.google.com [IPv6:2607:f8b0:4864:20::1136]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 8F84EC151086 for <crypto-panel@irtf.org>; Wed, 11 Oct 2023 01:56:25 -0700 (PDT)
Received: by mail-yw1-x1136.google.com with SMTP id 00721157ae682-5a7e5dc8573so2952567b3.0 for <crypto-panel@irtf.org>; Wed, 11 Oct 2023 01:56:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1697014584; x=1697619384; darn=irtf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=GRGP6yp65Y1KtOENN0wlA/O9dGu4BSLvqzzHhvihT/4=; b=Wd8wW740XX5UmJDXo4tYyVV+VmHx8bb+zz5inDkybCdvqs1lTGHQB1xKf+9Vg+71as /Evybjpeu4rdn/jVZdVjTQBTAqjpPez7P18skX5JYe0Zpli4DlddaFYzcLDxLpYEALvf YfwDWZyo7fsBCOObZ/Rsm0eUpmBsJglT1H59ZRuwAOhKtWLf25DhQLQtRRqFAsoYoaSU JziXzBw3OlVxcx7W6xIExbzn4Tb95gkWlX2WfGySdnyoA3TKjhVGgHOUt1KQdNoPZu8w bN5/5PCLY0aA1phbssHhOYUlXhq5VBe1phmZsyADJJFtoKzKR4re4cytmUp0xehGLdPy KwpA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697014584; x=1697619384; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=GRGP6yp65Y1KtOENN0wlA/O9dGu4BSLvqzzHhvihT/4=; b=B3uBS7Hi+q9bnT82vIILtSTxUIYBFfz/JJqPLmejdZ2AmqoBj/cvyIEFmOVF+kHwVU /MJejK8SL5HuHUWjMw7TjmLGP6omkibLNofrokP/CNGT30S/x2q96bEnqjjOYiQELGjw Ow7WEgHcH+dsRMuaoWmyIF6I/IJk0qYz8Q0rhhwoNwRFWvOn5gpuOyTYVHX0YsvH4k/Z H3YpuwJFljmxozyZC0LyGyJUCetkHy/ADvEr2H73jB3ia+WxtVLMnJfBz2/X+qpcm/Lk KpcTWbRCDAkB+O40JepOZvSo0kY6zLcpqGb1JN1oMGjzyMKGAEeT4wdsbbXicm+t8xV/ 0e2A==
X-Gm-Message-State: AOJu0YyY9QXEJMteNm8JWH+v9o3hU0bSGQcEzdb02MXplYrRkkjtW46X 3F9u1oqUzAL4H9HWK3UUGMZHYt3w8TWq6G7lqR1BC7AGQsfE3g==
X-Google-Smtp-Source: AGHT+IGoVz8O7yM7PSo+748sGi9KUzbKNmtf+S58MBq7aYKGnSG3Vh0gYWyD1K/LWL5dJHoxETUt9JLbdwNnXIQwAq4=
X-Received: by 2002:a5b:8f:0:b0:d85:eac0:c7d2 with SMTP id b15-20020a5b008f000000b00d85eac0c7d2mr18379570ybp.6.1697014584205; Wed, 11 Oct 2023 01:56:24 -0700 (PDT)
MIME-Version: 1.0
References: <CAMr0u6kAW_rEK3_7Y64nU=-DP=7JjXM-oiX1XB+_973yP+pf0w@mail.gmail.com> <CAMr0u6nPOnUDCvfZ7mM_8nYWcmbp3nt+jp1O7tAP7byMWWWgWw@mail.gmail.com>
In-Reply-To: <CAMr0u6nPOnUDCvfZ7mM_8nYWcmbp3nt+jp1O7tAP7byMWWWgWw@mail.gmail.com>
From: "Stanislav V. Smyshlyaev" <smyshsv@gmail.com>
Date: Wed, 11 Oct 2023 11:56:12 +0300
Message-ID: <CAMr0u6nu-mC0hQKQVBTwKB8jW=6Rn9eiibU-FN+p6ntJNwittQ@mail.gmail.com>
To: crypto-panel@irtf.org, Bjoern Tackmann <bjoern.tackmann@ieee.org>, Karthikeyan Bhargavan <karthik.bhargavan@gmail.com>, Karthik Bhargavan <karthikeyan.bhargavan@inria.fr>, Thomas Pornin <thomas.pornin=40nccgroup.com@dmarc.ietf.org>, Thomas Pornin <thomas.pornin@nccgroup.com>
Cc: draft-irtf-cfrg-cpace@ietf.org, cfrg-chairs@ietf.org
Content-Type: multipart/alternative; boundary="0000000000007868c806076cff2e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/crypto-panel/7FucX6mHa2Nsow3_fia4qOyYI74>
Subject: Re: [Crypto-panel] Request for review: CPace
X-BeenThere: crypto-panel@irtf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Crypto Review Panel review coordination <crypto-panel.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/crypto-panel>, <mailto:crypto-panel-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/crypto-panel/>
List-Post: <mailto:crypto-panel@irtf.org>
List-Help: <mailto:crypto-panel-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/crypto-panel>, <mailto:crypto-panel-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Oct 2023 08:56:29 -0000

Dear Bjoern, Karthik and Thomas,

The chairs would like to ask each of you to review the CPace draft, "CPace,
a balanced composable PAKE", draft-irtf-cfrg-cpace-10 (
https://datatracker.ietf.org/doc/draft-irtf-cfrg-cpace/).

There were a lot of reviews of the protocol and the early versions of the
draft, see https://github.com/cfrg/pake-selection
There were several important questions in those reviews which had to be
addressed during the evolution of the draft in CFRG: some of them are
underlined in the following paper: https://eprint.iacr.org/2021/839.pdf –
we would like to ask you to pay special attention to these issues.

It would be great if you could do it before the middle of November.

Best regards,
Stanislav (for CFRG chairs)

On Thu, Oct 5, 2023 at 10:51 AM Stanislav V. Smyshlyaev <smyshsv@gmail.com>
wrote:

> Hi all,
>
> We still need reviewers (three or four) for the CPace draft.
>
> Since CPace was a winner of the PAKE selection process, we have to be 100%
> sure that all concerns have been properly addressed.
>
> Bjoern, Russ, Karthik, we will be happy to receive reviews from you
> (taking into account your reviews provided during the PAKE Selection
> process).
>
> Chloe, Julia, Jean-Philippe, Scott, if some of you could review the CPace
> draft, despite the fact that you've just reviewed the OPAQUE draft (thanks
> a lot once again for this!), that would be amazing as well.
>
> Best regards,
> Stanislav (for CFRG chairs)
>
> On Mon, Sep 25, 2023 at 3:17 PM Stanislav V. Smyshlyaev <smyshsv@gmail.com>
> wrote:
>
>> Dear Crypto Panel Experts,
>>
>> The chairs would like to ask the Crypto Panel to provide three (or more)
>> reviews for the CPace draft, "CPace, a balanced composable PAKE",
>> draft-irtf-cfrg-cpace-10 (
>> https://datatracker.ietf.org/doc/draft-irtf-cfrg-cpace/).
>>
>> The CPace protocol was selected as a result of the PAKE selection process
>> in CFRG (as well as the OPAQUE protocol which has recently been reviewed by
>> the Panel).
>>
>> There were a lot of reviews of the protocol and the early versions of the
>> draft, see https://github.com/cfrg/pake-selection
>> There were several important questions in those reviews which had to be
>> addressed during the evolution of the draft in CFRG: some of them are
>> underlined in the following paper: https://eprint.iacr.org/2021/839.pdf
>>
>> Hence we would like to ask the reviewers to pay a lot of attention to
>> reviewing this draft, trying to take into account as many considerations
>> provided in the previous reviews as possible.
>>
>> Stanislav (on behalf of the CFRG Chairs)
>>
>

v2.23.0 | Report a Bug | By Email