IETF Logo Mail Archive

Re: [tcpm] tcp-auth-opt issue: support for NATs

Joe Touch <touch@ISI.EDU> Thu, 07 August 2008 18:52 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 CB1B83A6803; Thu, 7 Aug 2008 11:52:32 -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 C59A73A6803 for <tcpm@core3.amsl.com>; Thu, 7 Aug 2008 11:52:31 -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=[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 Gmk8H5JtIe4R for <tcpm@core3.amsl.com>; Thu, 7 Aug 2008 11:52:30 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id CDAB43A67F2 for <tcpm@ietf.org>; Thu, 7 Aug 2008 11:52:30 -0700 (PDT)
Received: from [192.168.10.101] (auto-66.185.38.62.wirelessworld.vi [66.185.38.62]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m77IqEJO026633 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 7 Aug 2008 11:52:17 -0700 (PDT)
Message-ID: <489B4436.1000807@isi.edu>
Date: Thu, 07 Aug 2008 11:51:34 -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: <4890F4BE.6060302@isi.edu> <396556a20807301622l4cb33deuff73cd13d7a75ba1@mail.gmail.com> <4890FBE8.1020203@isi.edu> <396556a20807311700w1eda50b0o5da7ae52e6c1691a@mail.gmail.com> <48935FFD.4090805@isi.edu> <396556a20808051826w1a839577q956f379f56db1165@mail.gmail.com> <20080806020257.D1C69525D8F@kilo.rtfm.com> <396556a20808061742y19f8f5fh78fe66bfe4d415be@mail.gmail.com> <20080807011812.DDC8050846@romeo.rtfm.com> <396556a20808071047q5bda8acbje7a8fc9f9bf2e597@mail.gmail.com> <20080807180512.77604529E4D@kilo.rtfm.com> <489B3B72.8030604@isi.edu> <20080807182005.04B5B52A03A@kilo.rtfm.com> <489B407A.6030001@isi.edu> <20080807185224.3A46750846@romeo.rtfm.com>
In-Reply-To: <20080807185224.3A46750846@romeo.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: support for NATs
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:
...
|> Supporting NATs can be done in two different ways:
|
| I think this is at least potentially an issue even aside from NAT. When
| I install keys on my host, you're proposing that I need to configure
| both the peer IP address and the key-id. This isn't necessarily
| bad, but it does mean that if (for instance) the other side decides
| to renumber, nothing will work absent manual reconfiguration. Is
| that something people want?

<indiv hat on>
If we ignore source IP addresses, we probably end up needing to go
through a set of possible keys when a SYN arrives. This seems like it
amplifies the impact of a SYN attack - the more keys we have, the more
each falsly-encrypted SYN costs.

Alternately, a good KMS could figure out when these IP addresses
changed, and update the TSAD accordingly. I would prefer this latter
solution...

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

iEYEARECAAYFAkibRDYACgkQE5f5cImnZrv3owCdHWgFR98s/2T9Hkcp+kr9p/Sp
mPQAnRjJWh2mK6g5xZGQ8IXct1VxD2FI
=uDIB
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm

v2.15.0 | Report a Bug | By Email