Re: [TLS] TLS 1.2 and hash agility for signatures

Martin Rex <martin.rex@sap.com> Mon, 19 March 2007 17:40 UTC

Return-path: <tls-bounces@lists.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTLqk-0004P5-Ds; Mon, 19 Mar 2007 13:40:50 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTLqh-0004Je-58 for tls@ietf.org; Mon, 19 Mar 2007 13:40:47 -0400
Received: from smtpde02.sap-ag.de ([155.56.68.170]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HTLqN-0002gv-Hk for tls@ietf.org; Mon, 19 Mar 2007 13:40:47 -0400
Received: from sap-ag.de (smtpde02) by smtpde02.sap-ag.de (out) with ESMTP id TAA28618; Mon, 19 Mar 2007 19:40:08 +0200 (MESZ)
From: Martin Rex <martin.rex@sap.com>
Message-Id: <200703191740.SAA07589@uw1048.wdf.sap.corp>
Subject: Re: [TLS] TLS 1.2 and hash agility for signatures
To: Pasi.Eronen@nokia.com
Date: Mon, 19 Mar 2007 18:40:03 +0100
In-Reply-To: <B356D8F434D20B40A8CEDAEC305A1F2403E566B1@esebe105.NOE.Nokia.com> from "Pasi.Eronen@nokia.com" at Mar 17, 7 07:28:45 pm
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-SAP: out
X-SAP: out
X-SAP: out
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: tls@ietf.org
X-BeenThere: tls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: martin.rex@sap.com
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/tls>
List-Post: <mailto:tls@lists.ietf.org>
List-Help: <mailto:tls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=subscribe>
Errors-To: tls-bounces@lists.ietf.org

Pasi.Eronen@nokia.com wrote:
> 
> Given that some signature algorithms have more tweakable parameters
> than just the hash algorithm (e.g. PSS has salt length, MGF and the
> MGF's hash algorithm), perhaps the simplest solution would be just to
> use DER-encoded AlgorithmIdentifier structures (instead of defining
> a new IANA-maintained number space just for TLS)? 
> 
> (Of course, a sane implementation probably wouldn't include a 
> DER encoder/decoder, but just list of octet strings for things it
> supports; e.g. 0x3021300906052b0e03021a05000414 for RSASSA-PKCS1-v1_5
> with SHA-1.)

Aren't the RSA-PSS additional parameters included in the algorithm
identifier structure, which results in a non-static Octetstring?
 
-Martin

_______________________________________________
TLS mailing list
TLS@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls