Re: [TLS] RSA-PSS in TLS 1.3

Yoav Nir <ynir.ietf@gmail.com> Tue, 01 March 2016 11:32 UTC

Return-Path: <ynir.ietf@gmail.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E4A01A1A70 for <tls@ietfa.amsl.com>; Tue, 1 Mar 2016 03:32:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GUQ4ZoDbcTLx for <tls@ietfa.amsl.com>; Tue, 1 Mar 2016 03:32:24 -0800 (PST)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2EB211A1A6E for <tls@ietf.org>; Tue, 1 Mar 2016 03:32:24 -0800 (PST)
Received: by mail-wm0-x22e.google.com with SMTP id n186so31979130wmn.1 for <tls@ietf.org>; Tue, 01 Mar 2016 03:32:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=AlDNcPBETBXSCpUmdS+Y4gBgWCi+1A6cy+sRYhNjyDE=; b=BaJRIpyJeLhei/9GLcnzFQeAoRG2oFcRmG/8JShMweFYvF/eL+h+Hd8eZQk0b/HmOu qAN6mW8jYgY9oPs0X9Fg+OGwIPP3LGoENSrNL4Iws46C1TAu/q/9gpZ2swd46IHOlsyB AmY9Wj4i96aBvRJkzUVp3wVbAHTcxEiUpXpiPg7ocFZwsYI+y1SfvbgIXwKe0satGAqG Qbzrf5wexNZfe5/Q84dPKsG/KnFYkpYEfPVhjFfl23S7ADnvrtqf1BeGn1oCknS3fGTx zdxPC94ZpeK0QEPwseLgp8VHQVZbgenvpu2iKVj3lWZ0D6aMsMWvoQaY6qQjzZdZuWMU xX+A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=AlDNcPBETBXSCpUmdS+Y4gBgWCi+1A6cy+sRYhNjyDE=; b=MWNzd1M7n5vSfRK/xHLMSYlHIVMXBGXSs+TpdB1najOf6rK7ipemKppd83Jeh1nj3F Daqq8doAFMXvNNfgMXhwTk4z1R/QSIJPl5wt0tuQJR1TmkIAj3XpDUq7cOzoxIKG3r3B eb2XmYr+2V+4aZKtvv7wjhSW5rE9BA0joGrvmKvZeDikrq58HFkDzstwdWvzvsrADmyc 1zowHG8YOHvihGpb1+ycsFPzFVQ/cLaEyj7K4Y1993FcHBLjORx3tV0lZmj9jsTSyOo0 r+W7BAsTwE0nHqj4VoTaQ2fB749KK/7F3uEFuPMZNSHio+RR5oy96IorfLw1+2jwlzb2 wtIA==
X-Gm-Message-State: AD7BkJKgXuvE5+v5Z9kh1n14FecSV+/VArLB8jojd2j36WJjFx5/ojIeStyeNclKjAn0Ng==
X-Received: by 10.28.175.139 with SMTP id y133mr3008831wme.45.1456831942768; Tue, 01 Mar 2016 03:32:22 -0800 (PST)
Received: from [172.24.251.185] (dyn32-131.checkpoint.com. [194.29.32.131]) by smtp.gmail.com with ESMTPSA id da6sm20975778wjb.24.2016.03.01.03.32.21 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 01 Mar 2016 03:32:22 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <CABkgnnX4Orgk7dvOtKN5FLryepf7Pb_bJtkxDiN+L7UUfthvSw@mail.gmail.com>
Date: Tue, 1 Mar 2016 13:32:20 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E3F402CD-24B4-4E86-B57B-45F6442645FB@gmail.com>
References: <CAOgPGoD=AAFDUXN8VkOHwTMEUm+-qi548NsicoD=1yQKSu-sng@mail.gmail.com> <CABkgnnX4Orgk7dvOtKN5FLryepf7Pb_bJtkxDiN+L7UUfthvSw@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/IeFfhIwLYtdgryviSZCQ-UnCoOA>
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] RSA-PSS in TLS 1.3
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2016 11:32:26 -0000

> On 1 Mar 2016, at 6:56 AM, Martin Thomson <martin.thomson@gmail.com> wrote:
> 
> On 1 March 2016 at 04:32, Joseph Salowey <joe@salowey.net> wrote:
>> We make RSA-PSS mandatory to implement (MUST implement instead of MUST
>> offer).   Clients can advertise support for PKCS-1.5 for backwards
>> compatibility in the transition period.
> 
>> From my perspective, this is fine.  I would like to say that we won't
> ever support PKCS#1.5 for TLS 1.3, but I think that I would rather
> have users on 1.3 with PKCS#1.5 than have them stuck on 1.2.
> 
> It seems like others are taking the position that we should say "MUST
> NOT use PKCS#1.5”.  

I’d go even further. I’d remove the rsapss(4) value from SignatureAlgorithm, leaving just rsa(1), and say that in TLS 1.3 an RSA signature is PSS just as it was PKCS#1.5 in TLS 1.2.

Certificates are a different issue altogether.

Yoav