Re: [TLS] Another IRINA bug in TLS

Peter Gutmann <> Sun, 24 May 2015 09:55 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id BB3331A89B9 for <>; Sun, 24 May 2015 02:55:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 5P3RPIU6mtzi for <>; Sun, 24 May 2015 02:55:30 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5634B1A89D3 for <>; Sun, 24 May 2015 02:55:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;;; q=dns/txt; s=mail; t=1432461330; x=1463997330; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=scsmZv8nD2MotyYiLwZ4SdbXMDCQgtID4ERj+CbH+9I=; b=e71fIl16vLQPu/1FkVx0CbUMsf9ccJR1SnbVOxwRwkDVDt03EyhyjcNW oVwvRFj8+JTvmLb+hWRXcvmkfQ3glkhV3hcEu8dk8KijIBuI5R3ImPsu6 GIbpNqRZlFWDjlNhF13Cx/mHdIh5C/Pdorhu8TozV4MjJPHNj+VeCsHUb wzyvgsJONS3kdQbDI6kayp2y/8ofx4B03M70+ceoDCFjR4+/VUw8pYo1O k3eN3GflFKAetRR5js3adVNIeD0ODx+xOvfgz9iLojxdTjy+dytCgh973 O9krTbTMjQzALt0rYryyyxCacqsIS0yEgZzFLSfB0CN+uH2eacE3ax88v w==;
X-IronPort-AV: E=Sophos;i="5.13,485,1427713200"; d="scan'208";a="17973073"
X-Ironport-Source: - Outgoing - Outgoing
Received: from ([]) by with ESMTP/TLS/AES128-SHA; 24 May 2015 21:55:25 +1200
Received: from ([]) by ([]) with mapi id 14.03.0174.001; Sun, 24 May 2015 21:55:24 +1200
From: Peter Gutmann <>
To: Karthikeyan Bhargavan <>
Thread-Topic: [TLS] Another IRINA bug in TLS
Thread-Index: AdCUn0KvC4ozoUHOQIKcwi120/Yv8P//W1SAgANHxkD//zphAIAA8y8g
Date: Sun, 24 May 2015 09:55:24 +0000
Message-ID: <>
References: <>, <> <>, <>
In-Reply-To: <>
Accept-Language: en-NZ, en-GB, en-US
Content-Language: en-NZ
x-originating-ip: []
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <>
Cc: "<>" <>
Subject: Re: [TLS] Another IRINA bug in TLS
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: Sun, 24 May 2015 09:55:34 -0000

Karthikeyan Bhargavan <> writes:

>The confusion between DSA and PKCS#3 has other unexpected consequences. As we
>describe in 3.5 of our Imperfect Forward Secrecy paper, some server
>implementations take a DSA group (p,q,g) and, when fitting it to TLS, confuse
>the “q” with the generator “g”. This bug leads to a rather nasty attack.
>(Yeah, you’d probably want to add this to the WTF category.)

It's a WTF, but it's the IETF's, not the implementers':

/* [...]

   For peculiar historical reasons (copying errors and the use of obsolete
   drafts as reference material) the X9.42 interpretation used in PKIX 
   reverses the second two parameters from FIPS 186 (so it uses p, g, q 
   instead of p, q, g), so when we read/write the parameter information we 
   have to switch the order in which we read the values if the algorithm 
   isn't DSA */