Re: [tcpm] feedcback on tcp-secure-05

Joe Touch <touch@ISI.EDU> Mon, 17 July 2006 04:57 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G2LAf-00079L-BN; Mon, 17 Jul 2006 00:57:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G2LAd-00079F-Cg for tcpm@ietf.org; Mon, 17 Jul 2006 00:57:27 -0400
Received: from vapor.isi.edu ([128.9.64.64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2LAc-00089d-1D for tcpm@ietf.org; Mon, 17 Jul 2006 00:57:27 -0400
Received: from [192.168.1.42] (pool-71-106-102-77.lsanca.dsl-w.verizon.net [71.106.102.77]) by vapor.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id k6H4ufH15175; Sun, 16 Jul 2006 21:56:41 -0700 (PDT)
Message-ID: <44BB1882.6030904@isi.edu>
Date: Sun, 16 Jul 2006 21:56:34 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: [tcpm] feedcback on tcp-secure-05
References: <0C53DCFB700D144284A584F54711EC5801D9592B@xmb-sjc-21c.amer.cisco.com> <7.0.1.0.0.20060715153423.08601b58@gont.com.ar>
In-Reply-To: <7.0.1.0.0.20060715153423.08601b58@gont.com.ar>
X-Enigmail-Version: 0.94.0.0
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: tcpm@ietf.org, "Anantha Ramaiah (ananth)" <ananth@cisco.com>
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0494870908=="
Errors-To: tcpm-bounces@ietf.org


Fernando Gont wrote:
> At 15:04 13/07/2006, Anantha Ramaiah \(ananth\) wrote:
> 
>> > The doc should also indicate that preventing these attacks
>> > does NOT prevent ICMP attacks (and cite Gont's draft in this
>> > regard); it would be useful for the security considerations
>> > to address whether ICMPs should be blocked altogether and
>> > what the impact of that would be. Without such blocking, it's
>> > not clear what the utility of this solution would be.
>>
>> Ok.
> 
> I don't think tcpsecure should make any advice on what to do with ICMP.
> 
> Just make it clear that the introduced mechanisms do not prevent
> ICMP-based attacks against TCP, and provide a pointer to
> draft-ietf-tcpm-icmp-attacks-00.txt .
> 
> If you are going to make any other statement on this issue, state that
> the ICMP-based attacks are easier to perform, and thus should be
> mitigated (if not, it's ICMP that is the "weakest link in the chain").
> 
> You could also add that, fortunately, virtually every implementation has
> mitigated the ICMP attacks described in
> draft-ietf-tcpm-icmp-attacks-00.txt, by implementing most (if not all)
> the counter-measures described in that draft.

That last point doesn't obviate the issue that ICMP packets - even
validated by the mitigations in the draft above - are still easier to
spoof and can be spoofed by third parties than any of the attacks in
tcp-secure.

I.e., they remain the weakest link, and worrying about tcp-secure
protections is nonsensical by comparison, UNLESS ICMPs are entirely
blocked.

Joe


_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www1.ietf.org/mailman/listinfo/tcpm