IETF Logo Mail Archive

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

Peter Gutmann <pgut001@cs.auckland.ac.nz> Thu, 12 September 2013 05:20 UTC

Return-Path: <pgut001@cs.auckland.ac.nz>
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 34C1621E812A; Wed, 11 Sep 2013 22:20:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 QiWtVMEBTDDE; Wed, 11 Sep 2013 22:20:53 -0700 (PDT)
Received: from mx2.auckland.ac.nz (mx2.auckland.ac.nz [130.216.125.245]) by ietfa.amsl.com (Postfix) with ESMTP id 3ABE721E812E; Wed, 11 Sep 2013 22:20:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=uoa; t=1378963248; x=1410499248; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=uWlLEbZZLdgXpTrt1h0LVJnFiQyGwJvyg5uqJeWMM0k=; b=iU9FWhMKo1zv9hEvE+xShVsxhhk9ueYeClUO6iVRmsbrqeF836sSq+G8 QNTrB/hRtyTgMvg/Cs5XEQXnpTP5+H7oVlzPQyMLn5AZhrLs2BQSa5pkw jSQNFNpIwKQ0420Wy51X0sSERcCnWj735lOBFCvDFGGLv95VXaFtKTXXN I=;
X-IronPort-AV: E=Sophos;i="4.90,888,1371038400"; d="scan'208";a="211759492"
X-Ironport-HAT: MAIL-SERVERS - $RELAYED
X-Ironport-Source: 130.216.4.112 - Outgoing - Outgoing
Received: from uxchange10-fe1.uoa.auckland.ac.nz ([130.216.4.112]) by mx2-int.auckland.ac.nz with ESMTP/TLS/AES128-SHA; 12 Sep 2013 17:20:44 +1200
Received: from UXCN10-TDC06.UoA.auckland.ac.nz ([169.254.11.187]) by uxchange10-fe1.UoA.auckland.ac.nz ([130.216.4.112]) with mapi id 14.02.0318.004; Thu, 12 Sep 2013 17:20:44 +1200
From: Peter Gutmann <pgut001@cs.auckland.ac.nz>
To: Eric Rescorla <ekr@rtfm.com>, Alfredo Pironti <alfredo@pironti.eu>, "perpass@ietf.org" <perpass@ietf.org>, "tls@ietf.org" <tls@ietf.org>
Thread-Topic: [TLS] Let's remove gmt_unix_time from TLS
Thread-Index: Ac6vd9PFx71XQUH1RkGmUyB65MA//g==
Date: Thu, 12 Sep 2013 05:20:42 +0000
Message-ID: <9A043F3CF02CD34C8E74AC1594475C735566D793@uxcn10-tdc06.UoA.auckland.ac.nz>
Accept-Language: en-NZ, en-GB, en-US
Content-Language: en-NZ
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.216.158.4]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Thu, 12 Sep 2013 05:21:01 -0000

Eric Rescorla <ekr@rtfm.com> writes:

>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?

Yes.  I've been putting random noise in the timestamp field for about 15
years (or more specifically I've never put a timestamp in the timestamp
field), no user has ever reported problems with this.

Peter.

v2.23.0 | Report a Bug | By Email