Re: [TLS] Interop failure due to wrong encoding of ServerDHParams

Hanno Böck <hanno@hboeck.de> Tue, 07 April 2015 12:31 UTC

Return-Path: <hanno@hboeck.de>
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 7EB631A8793 for <tls@ietfa.amsl.com>; Tue, 7 Apr 2015 05:31:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_BACK=2.3, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no
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 ox_Q3Lurhkol for <tls@ietfa.amsl.com>; Tue, 7 Apr 2015 05:31:35 -0700 (PDT)
Received: from zucker.schokokeks.org (zucker.schokokeks.org [178.63.68.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9130E1A878B for <tls@ietf.org>; Tue, 7 Apr 2015 05:31:35 -0700 (PDT)
Received: from pc1.fritz.box (x4d0c5d25.dyn.telefonica.de [::ffff:77.12.93.37]) (AUTH: LOGIN hanno-default@schokokeks.org, TLS: TLSv1/SSLv3, 128bits, ECDHE-RSA-AES128-GCM-SHA256) by zucker.schokokeks.org with ESMTPSA; Tue, 07 Apr 2015 14:31:33 +0200 id 000000000000005D.000000005523CE25.00000620
Date: Tue, 07 Apr 2015 14:31:48 +0200
From: Hanno Böck <hanno@hboeck.de>
To: tls@ietf.org
Message-ID: <20150407143148.2f76a26f@pc1.fritz.box>
In-Reply-To: <5523C7D5.8090703@redhat.com>
References: <5523C7D5.8090703@redhat.com>
X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.27; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=_zucker.schokokeks.org-1568-1428409893-0001-2"
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/DO33wva8Ij5Y7y7rgAo40jNLh6Y>
Subject: Re: [TLS] Interop failure due to wrong encoding of ServerDHParams
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: <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: Tue, 07 Apr 2015 12:31:37 -0000

On Tue, 07 Apr 2015 14:04:37 +0200
Florian Weimer <fweimer@redhat.com> wrote:

> I've encountered a TLS 1.2 server implementation which sometimes
> sends a ServerDHParams structure as part of the ServerKeyExchange
> message which indicates a length of 127 bytes for the dh_Ys
> parameter, but the parameter actually sent contains 128 bytes.  As a
> result, parsing the ServerKeyExchange message fails, leading to a
> handshake failure.  (Maybe this happens if the most significant byte
> of dh_Ys is zero.)

Hannes from ocaml-tls said something very similar a few days ago in a
talk at CCC Berlin. But I think he also said he observed something like
that on their servers, but doesn't know which implementation caused it.

The talk was streamed and recorded, but I think it's not online yet.


-- 
Hanno Böck
http://hboeck.de/

mail/jabber: hanno@hboeck.de
GPG: BBB51E42