IETF Logo Mail Archive

Re: [tcpm] tcp-auth-opt issue: replay protection

Joe Touch <touch@ISI.EDU> Wed, 06 August 2008 15:05 UTC

Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 27C7A28C393; Wed, 6 Aug 2008 08:05:07 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D289D28C354 for <tcpm@core3.amsl.com>; Wed, 6 Aug 2008 08:05:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.527
X-Spam-Level:
X-Spam-Status: No, score=-1.527 tagged_above=-999 required=5 tests=[AWL=1.072, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yXA6CJw0wCzl for <tcpm@core3.amsl.com>; Wed, 6 Aug 2008 08:05:04 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 98EAF28C358 for <tcpm@ietf.org>; Wed, 6 Aug 2008 08:05:04 -0700 (PDT)
Received: from [192.168.2.121] (bolongo.jbtelenet.com [204.11.152.116]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m76F4JHv006690 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 6 Aug 2008 08:04:36 -0700 (PDT)
Message-ID: <4899BD4A.9040509@isi.edu>
Date: Wed, 06 Aug 2008 08:03:38 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: Eric Rescorla <ekr@networkresonance.com>
References: <20080728042451.C7A174B7AD3@kilo.rtfm.com> <488DD77D.9070608@isi.edu> <20080728144721.AC9184B905A@kilo.rtfm.com> <488DE021.7070307@isi.edu> <20080728164013.422D14B9600@kilo.rtfm.com> <F32F8EC5-70C9-4A7B-A2D2-B00CA43AECFA@nokia.com> <20080730213253.B347F4D52E1@kilo.rtfm.com> <4890E9AE.3000607@isi.edu> <20080731001609.6511C4D5E34@kilo.rtfm.com> <489175BD.6040201@isi.edu> <396556a20807311010k78c22981xa0eebd1b46e9f619@mail.gmail.com> <48935983.80701@isi.edu> <3FBA635A-0473-4B58-86E2-C7523A35CE24@nokia.com> <20080806133734.7721D527252@kilo.rtfm.com>
In-Reply-To: <20080806133734.7721D527252@kilo.rtfm.com>
X-Enigmail-Version: 0.95.6
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Adam Langley <agl@imperialviolet.org>, tcpm@ietf.org
Subject: Re: [tcpm] tcp-auth-opt issue: replay protection
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Eric Rescorla wrote:
| At Wed, 6 Aug 2008 14:32:02 +0300,
| Lars Eggert wrote:
|> On 2008-8-1, at 21:44, ext Joe Touch wrote:
|>> IMO: retransmitted packets would use the currently active keyID
|>> (even if
|>> different from what was previously transmitted).
|> I agree. TCP retransmits previous data, not previous segments.
|
| I agree it should be permissible to use the new key-id, but
| should it be required? I don't know a lot about
| TCP stack implementations, but do any of them currently save
| existing packets and just retransmit them? That's legal, right?
| If so, this would break that.

<indiv hat on>
Does anyone know what happens to other options? I.e., aren't timestamps
recomputed, SACK options recalculated, etc.? It seems like the options
need to be revisited when a segment goes out the door anyway, and a
stack that just replays segments is what might be considered "broken"...

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkiZvUoACgkQE5f5cImnZrsYNgCfTbiRWhSyUB+94q7Vael7jvNR
uwUAoJiVPk7mSlkaFhgrrJglhCowQ0B7
=y3nm
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm

v2.23.0 | Report a Bug | By Email