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

"Stanislav V. Smyshlyaev" <smyshsv@gmail.com> Fri, 12 January 2024 06:08 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 47F1FC14F6B1 for <crypto-panel@ietfa.amsl.com>; Thu, 11 Jan 2024 22:08:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 lPzhxy-aM8eN for <crypto-panel@ietfa.amsl.com>; Thu, 11 Jan 2024 22:08:13 -0800 (PST)
Received: from mail-yb1-xb35.google.com (mail-yb1-xb35.google.com [IPv6:2607:f8b0:4864:20::b35]) (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 11372C14F6AE for <crypto-panel@irtf.org>; Thu, 11 Jan 2024 22:08:12 -0800 (PST)
Received: by mail-yb1-xb35.google.com with SMTP id 3f1490d57ef6-dbdb124491cso4836119276.1 for <crypto-panel@irtf.org>; Thu, 11 Jan 2024 22:08:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1705039692; x=1705644492; 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=Pn5WkoiQFtUzb/PuzR9/AjdAT4OUeG/6U0+lKV+UHs4=; b=W6ccYkE3/cYbsBuRLqiQ/V7JzjH95OXYitFhvRDy5YmM1Xs2ciy/UpdEcnDrGkCHZo 1a0graLh2ntpUOLdS1gJZagowNSEBUc+HUG/aJYSIukoLWDJjA1nuisxOsKnAmFfBTp8 e0t0E1QNYpc4KOcITIKkldeZQWJyFnARTRVb8lQWyA9lDUlpRkFZceskemKlbSNMb5J6 f7OXcPpOFhiCJOH9JOVmkNAOj9x3vQWUNwMJMMPNx/x+VWltbNDUMsRdcYtO9cHxOiT3 gPFJnksQhV8vdwy0v00MoBYRsY4CBjjSttl+EtQUeEhmbLZZITknYfwVz4HyDiytHc5/ rvGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705039692; x=1705644492; 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=Pn5WkoiQFtUzb/PuzR9/AjdAT4OUeG/6U0+lKV+UHs4=; b=SaUtyibH2AkhVPTDmYDc9+iTJmEurxDJo4b/unRIiBtc/zK0om8wFt8gaNU3KpQUWO JWlf3uXGgdkudeAgFZ5F3VkG+pTyTei9UMm8TchWlon2IbK9tujdRKGZKLoXltZcFGcH 0vRjB277KS1MD+LnC+6vnFa6sDA9b+RP90JoV3vqldYrkOHZDjKgaJ4Z4j4vI5KJVBfo SwjVFPlkX705C9cm2T2nqYn+smp3m0Kh4NgqdWKMzzVY1OoXrT5jrynl5LvtJNU4n8f1 WVxCguhwUb6DZs+AZ6lpaIdV7D528WAoUgqebhD5B2QKOiaYSWwcCO67FBtKKdGn85Ev iOjw==
X-Gm-Message-State: AOJu0YzcTJX4sIkep6HswtyrE5G60UyHyFvmySdgDLkUNQE+37grwFLn KHXoijfYJkLWI5y062QgTl17xr24RLuWybgCxFc=
X-Google-Smtp-Source: AGHT+IH9AcPGvPd+d0r02tIEcVTAhxdN9rd8sMRN3BmHtDn5K0eO9WhY17pfLKtHvSwilGu8YyJz8Jus8iREDt/8v7I=
X-Received: by 2002:a25:2f55:0:b0:dbf:50bc:187f with SMTP id v82-20020a252f55000000b00dbf50bc187fmr174549ybv.59.1705039691819; Thu, 11 Jan 2024 22:08:11 -0800 (PST)
MIME-Version: 1.0
References: <CAMr0u6kAW_rEK3_7Y64nU=-DP=7JjXM-oiX1XB+_973yP+pf0w@mail.gmail.com> <CAMr0u6nPOnUDCvfZ7mM_8nYWcmbp3nt+jp1O7tAP7byMWWWgWw@mail.gmail.com> <CAMr0u6nu-mC0hQKQVBTwKB8jW=6Rn9eiibU-FN+p6ntJNwittQ@mail.gmail.com> <D94E0BE0-0C11-41B8-9479-F4A355B54164@inria.fr>
In-Reply-To: <D94E0BE0-0C11-41B8-9479-F4A355B54164@inria.fr>
From: "Stanislav V. Smyshlyaev" <smyshsv@gmail.com>
Date: Fri, 12 Jan 2024 09:08:00 +0300
Message-ID: <CAMr0u6mx_3rNAa7BL1A=F505T4wRa+F3qAGSNndGCOW9otJuMw@mail.gmail.com>
To: Karthikeyan Bhargavan <karthikeyan.bhargavan@inria.fr>
Cc: crypto-panel@irtf.org, Bjoern Tackmann <bjoern.tackmann@ieee.org>, Karthikeyan Bhargavan <karthik.bhargavan@gmail.com>, Thomas Pornin <thomas.pornin=40nccgroup.com@dmarc.ietf.org>, Thomas Pornin <thomas.pornin@nccgroup.com>, draft-irtf-cfrg-cpace@ietf.org, cfrg-chairs@ietf.org
Content-Type: multipart/alternative; boundary="00000000000028b0cf060eb97db3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/crypto-panel/ZUW4-SFj8AooBIJB_Br96lnj49I>
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://mailman.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://mailman.irtf.org/mailman/listinfo/crypto-panel>, <mailto:crypto-panel-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jan 2024 06:08:18 -0000

Hi Karthik,

Any news with the review?

Regards,
Stanislav (for CFRG chairs)

On Wed, Oct 11, 2023 at 12:00 PM Karthikeyan Bhargavan <
karthikeyan.bhargavan@inria.fr> wrote:

> Ok. I will put this on my stack.
>
> All my best,
> Karthik
>
> On 11 Oct 2023, at 10:56, Stanislav V. Smyshlyaev <smyshsv@gmail.com>
> wrote:
>
> 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)
>>>
>>
>