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

"Stanislav V. Smyshlyaev" <smyshsv@gmail.com> Thu, 05 October 2023 07:51 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 A45D1C1526F4 for <crypto-panel@ietfa.amsl.com>; Thu, 5 Oct 2023 00:51:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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_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 8bGfbNf744IF for <crypto-panel@ietfa.amsl.com>; Thu, 5 Oct 2023 00:51:52 -0700 (PDT)
Received: from mail-yw1-x1134.google.com (mail-yw1-x1134.google.com [IPv6:2607:f8b0:4864:20::1134]) (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 0ECDFC14CE5D for <crypto-panel@irtf.org>; Thu, 5 Oct 2023 00:51:52 -0700 (PDT)
Received: by mail-yw1-x1134.google.com with SMTP id 00721157ae682-59c215f2f4aso7241497b3.1 for <crypto-panel@irtf.org>; Thu, 05 Oct 2023 00:51:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696492311; x=1697097111; 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=H+oLyRaRAd5EspgsSHQjeNWFr4B030y10vIgLC67JoM=; b=ZFxo1/OLTnXby+C9c+qpfUq/FiU1j3pPkAXQeAd7hPq6OYSIbVGoOGOGxTN/+q2fp5 yo0rgT73P/T6FLZ1YMYXcQIGo9lE8oD2zURCoEzZfZ/pmgumHCujxFNWpOw6/n74n6Cw XC5oaWOQSrPPNgqqRTIrDFTs5gvg0vfkLzaURnzhEyDQjnwQVfNgR5QE+8FhFlSrkJlu w4F3VLf1eeWJbzHRho4W0SeYwnq5GqcGnuiDjofvDhgBhx8AoCCkUeHcbj0BJcDYDT0X jQBnVdqC/M2oAzapzhbsvzkMAmzfHzQuuTH6uy3J5gkwhA0lvsWmTminVUOqpmRjUa4h JwtQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696492311; x=1697097111; 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=H+oLyRaRAd5EspgsSHQjeNWFr4B030y10vIgLC67JoM=; b=LUv44Wi6Mwo279Zy5H/Pcj5km2cpjhlnRO65B5RnfStQVFkcao4szqYcTP2RGtGkET KZsc/xdIweLyD2z804Y/7k6GqMtbwPhjA3lrhVI1KSRE0oKD6L+ubqqIzxwSWeSMKnaS 7zvl/yj+ja/NjThaRtakIrrZQ1OKWgXTmtN8mMvnLtF17bvURaLiBoWHFsb1qvHTa8M+ I2dn8elPSmdVSBc0B20/SgS7UfBmEBIsIPRi3MZBjmTr5c0q4Z0G2SCpQJkt5ZKR+4av DOb6u48l8VfH/w/JjziVguLDKueK1m6szam3aJ0trAbN1nTduSKMLUoUBf8yP9tTKcg/ tiGw==
X-Gm-Message-State: AOJu0YxwAfQarcgvQnMGBqn/Dw708hOy28MslmGAtYdUX/wsSLXtMyA6 ecR+rBnQcipRjxHyOPrEeZ6iyDQd9+SeJ0RMJvM/hidv3TxViA==
X-Google-Smtp-Source: AGHT+IFIoNbwGvlfQ7YRlfVGxFVSWwb0rEigq0XEYHY+XcDf6amvHXJSWtwvgXnO5w5Ho5sjfVzYjpifrkz63GQBCro=
X-Received: by 2002:a25:b222:0:b0:d86:54f0:7bed with SMTP id i34-20020a25b222000000b00d8654f07bedmr4132755ybj.42.1696492310731; Thu, 05 Oct 2023 00:51:50 -0700 (PDT)
MIME-Version: 1.0
References: <CAMr0u6kAW_rEK3_7Y64nU=-DP=7JjXM-oiX1XB+_973yP+pf0w@mail.gmail.com>
In-Reply-To: <CAMr0u6kAW_rEK3_7Y64nU=-DP=7JjXM-oiX1XB+_973yP+pf0w@mail.gmail.com>
From: "Stanislav V. Smyshlyaev" <smyshsv@gmail.com>
Date: Thu, 05 Oct 2023 10:51:39 +0300
Message-ID: <CAMr0u6nPOnUDCvfZ7mM_8nYWcmbp3nt+jp1O7tAP7byMWWWgWw@mail.gmail.com>
To: crypto-panel@irtf.org
Cc: draft-irtf-cfrg-cpace@ietf.org, cfrg-chairs@ietf.org
Content-Type: multipart/alternative; boundary="0000000000008ba0970606f36515"
Archived-At: <https://mailarchive.ietf.org/arch/msg/crypto-panel/Xo84ud5uXE1zVrh48V_zIoYE49s>
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: Thu, 05 Oct 2023 07:51:55 -0000

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)
>