Re: [TLS] Using RSA PSS in TLS

mrex@sap.com (Martin Rex) Thu, 22 January 2015 02:06 UTC

Return-Path: <mrex@sap.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 055511A00D1 for <tls@ietfa.amsl.com>; Wed, 21 Jan 2015 18:06:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.551
X-Spam-Level:
X-Spam-Status: No, score=-6.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-5, 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 be6rY8otjxGw for <tls@ietfa.amsl.com>; Wed, 21 Jan 2015 18:06:48 -0800 (PST)
Received: from smtpde01.smtp.sap-ag.de (smtpde01.smtp.sap-ag.de [155.56.68.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C69A31A00DC for <tls@ietf.org>; Wed, 21 Jan 2015 18:06:27 -0800 (PST)
Received: from mail05.wdf.sap.corp (mail05.sap.corp [194.39.131.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtpde01.smtp.sap-ag.de (Postfix) with ESMTPS id 9674F3A318; Thu, 22 Jan 2015 03:06:25 +0100 (CET)
Received: from ld9781.wdf.sap.corp (ld9781.wdf.sap.corp [10.21.82.193]) by mail05.wdf.sap.corp (Postfix) with ESMTP id 481B542828; Thu, 22 Jan 2015 03:06:25 +0100 (CET)
Received: by ld9781.wdf.sap.corp (Postfix, from userid 10159) id 3CCCB1B10F; Thu, 22 Jan 2015 03:06:25 +0100 (CET)
In-Reply-To: <9A043F3CF02CD34C8E74AC1594475C73AAF5D521@uxcn10-tdc05.UoA.auckland.ac.nz>
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>
Date: Thu, 22 Jan 2015 03:06:25 +0100
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20150122020625.3CCCB1B10F@ld9781.wdf.sap.corp>
From: mrex@sap.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/1V5CWfchzBRu2ycFJe4GkmWHhvA>
Cc: "<tls@ietf.org>" <tls@ietf.org>
Subject: Re: [TLS] Using RSA PSS in TLS
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
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: <http://www.ietf.org/mail-archive/web/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: Thu, 22 Jan 2015 02:06:50 -0000

Peter Gutmann wrote:
> <mpg@polarssl.org> writes:
> 
>>Appparently [1] NSS and BoringSSL has been doing that for a few months now
>>(though NSS seems to take steps to allow some variation), maybe they could
>>provide some feedback?
>>
>>[1]: https://www.imperialviolet.org/2014/09/26/pkcs1.html
> 
> I've been doing this for ages, and I believe OpenSSL does as well(?).  Never
> had any problems (or at least none reported) so far...

Btw. TLSv1.2 explicitly requires support for a slight variation
(NULL and absent parameters) on the TLSv1.2 RSA PKCS#1 v1.5
digitally-signed signature verification, see rfc5246,
section 4.7 3rd paragraph:

  https://tools.ietf.org/html/rfc5246#section-4.7

   In RSA signing, the opaque vector contains the signature generated
   using the RSASSA-PKCS1-v1_5 signature scheme defined in [PKCS1].  As
   discussed in [PKCS1], the DigestInfo MUST be DER-encoded [X680]
   [X690].  For hash algorithms without parameters (which includes
   SHA-1), the DigestInfo.AlgorithmIdentifier.parameters field MUST be
   NULL, but implementations MUST accept both without parameters and
   with NULL parameters.  Note that earlier versions of TLS used a
   different RSA signature scheme that did not include a DigestInfo
   encoding.


-Martin