IETF Logo Mail Archive

Re: [CFRG] RSA decryption issues - Implementation Guidance - Marvin Attack

"Salz, Rich" <rsalz@akamai.com> Tue, 10 October 2023 15:26 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 101A2C151991 for <cfrg@ietfa.amsl.com>; Tue, 10 Oct 2023 08:26:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.805
X-Spam-Level:
X-Spam-Status: No, score=-2.805 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=akamai.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 LQvNkDW7xcwT for <cfrg@ietfa.amsl.com>; Tue, 10 Oct 2023 08:26:54 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A954C151079 for <cfrg@irtf.org>; Tue, 10 Oct 2023 08:26:54 -0700 (PDT)
Received: from pps.filterd (m0122332.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.17.1.22/8.17.1.22) with ESMTP id 39AEP8D9003998; Tue, 10 Oct 2023 16:26:49 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h= from:to:cc:subject:date:message-id:references:in-reply-to :content-type:mime-version; s=jan2016.eng; bh=Bi7NZoFT9oNFCNU6E1 Z9GHFd26bSCQF/5J2vLUpqqTQ=; b=erRdrfBEYLJSk0W2/PbM16FuXvDO34MoPL A4GKIM6C83uGF/ls8HVTK4gj6V8ok2vfJ/JuMfthaXtKxWexCpEyGEAr02uLpB1L UyvRWdbt94NYiGihg8zw0eK7pUvJBgYhhsutY06O9EH2mbfojpL2q0p6oUBozqWg z/RAkrvZr02EmZeKnMYqxb98DqwRqW2uBHIqG3JTejR7AjBFEHXhjlMS9kV2im39 aMqte8IXnUdM88JfB4EFYNybEFPgxEfflLublr1XrtRzC5PPKZjG0HyXNCCP/b3R toBCH9kEKq0rLr9nDn+es7Taj75zL8yzQFSpG24qr3LCJ4QfM3kQ==
Received: from prod-mail-ppoint4 (a72-247-45-32.deploy.static.akamaitechnologies.com [72.247.45.32] (may be forged)) by mx0a-00190b01.pphosted.com (PPS) with ESMTPS id 3tkhrvgeq3-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 10 Oct 2023 16:26:49 +0100 (BST)
Received: from pps.filterd (prod-mail-ppoint4.akamai.com [127.0.0.1]) by prod-mail-ppoint4.akamai.com (8.17.1.19/8.17.1.19) with ESMTP id 39ADHfv7028431; Tue, 10 Oct 2023 11:26:48 -0400
Received: from email.msg.corp.akamai.com ([172.27.50.202]) by prod-mail-ppoint4.akamai.com (PPS) with ESMTPS id 3tmfas0rpq-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 10 Oct 2023 11:26:47 -0400
Received: from ustx2ex-dag4mb4.msg.corp.akamai.com (172.27.50.203) by ustx2ex-dag4mb3.msg.corp.akamai.com (172.27.50.202) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.25; Tue, 10 Oct 2023 08:26:47 -0700
Received: from ustx2ex-dag4mb4.msg.corp.akamai.com ([172.27.50.203]) by ustx2ex-dag4mb4.msg.corp.akamai.com ([172.27.50.203]) with mapi id 15.02.1258.025; Tue, 10 Oct 2023 08:26:47 -0700
From: "Salz, Rich" <rsalz@akamai.com>
To: Neil Madden <neil.e.madden@gmail.com>, Hubert Kario <hkario@redhat.com>
CC: "cfrg@irtf.org" <cfrg@irtf.org>
Thread-Topic: [CFRG] RSA decryption issues - Implementation Guidance - Marvin Attack
Thread-Index: AQHZ+37rPstSDFRzRkSmGK7ujxblD7BDl02A///AXIA=
Date: Tue, 10 Oct 2023 15:26:47 +0000
Message-ID: <EF2E7DB1-DAFD-4BC2-897D-C157336895D5@akamai.com>
References: <3a593a35-95b1-41dd-b5b6-9ba1adc67a1c@redhat.com> <79F6E56D-2AF5-435E-A21F-9A5360648010@gmail.com>
In-Reply-To: <79F6E56D-2AF5-435E-A21F-9A5360648010@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.77.23091003
x-originating-ip: [172.27.164.43]
Content-Type: multipart/alternative; boundary="_000_EF2E7DB1DAFD4BC2897DC157336895D5akamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.267,Aquarius:18.0.980,Hydra:6.0.619,FMLib:17.11.176.26 definitions=2023-10-10_10,2023-10-10_01,2023-05-22_02
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxlogscore=576 adultscore=0 bulkscore=0 malwarescore=0 phishscore=0 spamscore=0 mlxscore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2309180000 definitions=main-2310100113
X-Proofpoint-GUID: hx5T6yPtf5NkhgAkVeZ6iG13Wn5pj9R6
X-Proofpoint-ORIG-GUID: hx5T6yPtf5NkhgAkVeZ6iG13Wn5pj9R6
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.267,Aquarius:18.0.980,Hydra:6.0.619,FMLib:17.11.176.26 definitions=2023-10-10_10,2023-10-10_01,2023-05-22_02
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxscore=0 lowpriorityscore=0 malwarescore=0 clxscore=1011 impostorscore=0 bulkscore=0 adultscore=0 mlxlogscore=585 priorityscore=1501 phishscore=0 suspectscore=0 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.19.0-2309180000 definitions=main-2310100113
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/PPGqCn29y102DRGKgcrGxZnG15w>
Subject: Re: [CFRG] RSA decryption issues - Implementation Guidance - Marvin Attack
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cfrg/>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Oct 2023 15:26:58 -0000

Ø Can a CFRG RFC update that IETF WG RFC to deprecate the algorithm?



No.  It would have to come from the IETF side of the house.

v2.37.1 | Report a Bug | By Email | System Status