Re: [TLS] RSA-PSS in TLS 1.3

"Dang, Quynh (Fed)" <> Thu, 03 March 2016 14:21 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 7C65B1ACE8B for <>; Thu, 3 Mar 2016 06:21:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.602
X-Spam-Status: No, score=-1.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Vc9xHhYWH5NX for <>; Thu, 3 Mar 2016 06:21:03 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 56C401ACE88 for <>; Thu, 3 Mar 2016 06:21:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1-nist-gov; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=nbHSS51bIx2kl/ekVOwPwGx0GqI95xLBwy4n++PEuEs=; b=NksYsHq3idFYAd8uOiDCcd2r5FyGdRDWN+NXRGzSBcUJi3YcbJ+Gk9S6/2moSRJDeuVB3lLv1mLZhmy0tO5LJ/bLUXFdWG0mVuRAIBFH2jp4BefgoPH5U42b8uQ0q8iqaz2OEsHwzBsNlBejTb2wuzCmY9YpLA23U2ZTtZzSCU4=
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.1.415.20; Thu, 3 Mar 2016 14:21:01 +0000
Received: from ([]) by ([]) with mapi id 15.01.0415.024; Thu, 3 Mar 2016 14:21:01 +0000
From: "Dang, Quynh (Fed)" <>
To: =?iso-8859-1?Q?Hanno_B=F6ck?= <>, "" <>
Thread-Topic: [TLS] RSA-PSS in TLS 1.3
Date: Thu, 3 Mar 2016 14:21:01 +0000
Message-ID: <>
References: <> <> <> <> <>, <20160303144947.0402bad9@pc1>
In-Reply-To: <20160303144947.0402bad9@pc1>
Accept-Language: en-US
Content-Language: en-US
authentication-results:; dkim=none (message not signed) header.d=none;; dmarc=none action=none;
x-originating-ip: []
x-microsoft-exchange-diagnostics: 1; BN1PR09MB123; 5:e/EzFOIePuio3vIb4Q4e5yUVwBxq40ibI7oo4MhPrTRefDfDqyAz6wiC25NSCVHl96sVOKFlLjHZLE9pZ4kGZkuYvePWRhfR5uZr/Row+kMmnyNR0+d3kFdK9Wdp4iUfbFDj/O/XJdAVOWkIb7Ip5Q==; 24:PyT8BnjXx4Ao8kJ4TrdKsaDZY+I95APurYNSOuGCdiL1D5fJXiQ8U4nhMUl66RZXvYn9QH0dd347KqKy/vndjlHpr6JFNYFJYq57fNZ76tY=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BN1PR09MB123;
x-ms-office365-filtering-correlation-id: e1085a87-2d6f-45c5-5663-08d3436f0c60
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-test: UriScan:(66011452539121);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046); SRVR:BN1PR09MB123; BCL:0; PCL:0; RULEID:; SRVR:BN1PR09MB123;
x-forefront-prvs: 0870212862
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(979002)(6009001)(243025005)(377454003)(24454002)(86362001)(97736004)(107886002)(19580395003)(5001770100001)(19580405001)(189998001)(122556002)(40100003)(10400500002)(76176999)(2501003)(54356999)(50986999)(74316001)(102836003)(5004730100002)(5003600100002)(3900700001)(11100500001)(5002640100001)(93886004)(1220700001)(1096002)(2950100001)(5008740100001)(3280700002)(2900100001)(2906002)(33656002)(15975445007)(99286002)(66066001)(77096005)(3846002)(6116002)(5001960100004)(586003)(92566002)(87936001)(106116001)(76576001)(3660700001)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:BN1PR09MB123;; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en;
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Mar 2016 14:21:01.4317 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2ab5d82f-d8fa-4797-a93e-054655c61dec
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN1PR09MB123
Archived-At: <>
Subject: Re: [TLS] RSA-PSS in TLS 1.3
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." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 03 Mar 2016 14:21:07 -0000

Hi Hanno,

I think the PSS uses a random salt to get the hashing probabilistic.

A customized version of a SHAKE can/may take a domain-separation string or/and a random salt.


From: TLS <> on behalf of Hanno Böck <>
Sent: Thursday, March 3, 2016 8:49 AM
Subject: Re: [TLS] RSA-PSS in TLS 1.3

On Thu, 3 Mar 2016 13:35:46 +0000
"Dang, Quynh (Fed)" <> wrote:

> Why don't we use an even more elegant RSA signature called "
> full-domain hash RSA signature" ?

Full Domain Hashing was originally developed by Rogaway and Bellare and
then later dismissed because they found that they could do better. Then
they developed PSS.


So in essence FDH is a predecessor of PSS and the authors of both
schemes came to the conclusion that PSS is the superior scheme.

> As you know, a SHAKE (as a variable output-length hash function)
> naturally produces a hash value which fits any given modulus size.
> Therefore, no paddings are needed which avoids any potential issues
> with the paddings and the signature algorithm would be very simple.

You could also use SHAKE in PSS to replace MGF1. This is probably
desirable if you intent to use PSS with SHA-3.

PSS doesn't really have any padding in the traditional sense. That is,
all the padding is somehow either hashed or xored with a hashed value.
I don't think any of the padding-related issues apply in any way to
PSS, if you disagree please explain.

(shameless plug: I wrote my thesis about PSS, in case anyone wants to
read it: - it's been a while, don't be too
hard on me if I made mistakes)

Hanno Böck