IETF Logo Mail Archive

Re: [TLS] Let's remove gmt_unix_time from TLS

<p.j.bakker@polarssl.org> Wed, 11 September 2013 16:42 UTC

Return-Path: <p.j.bakker@offspark.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D031211E8192 for <tls@ietfa.amsl.com>; Wed, 11 Sep 2013 09:42:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level:
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KFNf2zupvrrj for <tls@ietfa.amsl.com>; Wed, 11 Sep 2013 09:42:39 -0700 (PDT)
Received: from vps2.brainspark.nl (vps2.brainspark.nl [141.138.204.106]) by ietfa.amsl.com (Postfix) with ESMTP id 0E4D221E8149 for <tls@ietf.org>; Wed, 11 Sep 2013 09:42:26 -0700 (PDT)
Received: from ip54507da9.speed.planet.nl ([84.80.125.169] helo=Slimpy) by vps2.brainspark.nl with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <p.j.bakker@offspark.com>) id 1VJnP8-0000Ui-17 for tls@ietf.org; Wed, 11 Sep 2013 18:36:34 +0200
From: p.j.bakker@polarssl.org
Sender: Paul Bakker <p.j.bakker@offspark.com>
To: tls@ietf.org
References: <CAKDKvuw240Ug4xB3zi2w0y7pUvCwSe0nNFZ2XP2vL-tbtKT0tg@mail.gmail.com> <CALR0uiJ0+yvcuYG69pSaaJntJwta-odJJQRMxQJWgVXKvUp3wQ@mail.gmail.com> <CABcZeBMY+iFgoq8E0hw8yYimqadTYN6CVfy-Ya1tAkbmsigAJQ@mail.gmail.com> <CAKDKvuw-YLexTwDf1SV_M4L129W+4CVL0mcJ8hGrx+ff3ts=Zg@mail.gmail.com>
In-Reply-To: <CAKDKvuw-YLexTwDf1SV_M4L129W+4CVL0mcJ8hGrx+ff3ts=Zg@mail.gmail.com>
Date: Wed, 11 Sep 2013 18:42:19 +0200
Message-ID: <004f01ceaf0d$e4f0e030$aed2a090$@polarssl.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQGw89OdAzuRzNVjwsYPHKl/X1BIawGYczkMAVpxk0MCAfYBDJnUivQw
Content-Language: nl
X-SA-Exim-Connect-IP: 84.80.125.169
X-SA-Exim-Mail-From: p.j.bakker@offspark.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on vps2.brainspark.nl)
Subject: Re: [TLS] Let's remove gmt_unix_time from TLS
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 11 Sep 2013 16:48:15 -0000

I can confirm that PolarSSL has no issues with receiving random data instead
of the timestamp.

On Wed, Sep 11, 2013 at 12:06 PM, Eric Rescorla <ekr@rtfm.com> wrote:
> Before we discuss mechanisms, it would be good to verify that in
> general clients and servers don't become unhappy if the timestamp is
> radically wrong. Has someone done measurements to verify that this is
> in fact the case at a broad scale?

v2.23.0 | Report a Bug | By Email