[70384] in North American Network Operators' Group
Re: BGP Exploit
daemon@ATHENA.MIT.EDU (Danny McPherson)
Wed May 12 17:51:33 2004
In-Reply-To: <71E4603E9370D51190A90080C82D91BB794D7F@mail.office.avensys.net>
From: Danny McPherson <danny@tcb.net>
Date: Wed, 12 May 2004 15:50:52 -0600
To: NANOG <nanog@merit.edu>
Errors-To: owner-nanog-outgoing@merit.edu
On May 12, 2004, at 2:41 PM, Mark Johnson wrote:
>
> What if sessions were attacked without MD5 in place. We would just see
> session resets. As these happen anyway frequently at peering points is
> there
> any straightforward way to determine if the vulnerability caused the
> reset?
Depends on why it happens frequently. If it happens because
you've got Network/Transport Layer or underlying connection problems
then there's some other brokenness you should probably be more
concerned with.
If you're referring to session resets because of a peer or user
action then something akin to "Last reset due to FOO" can likely
be gleaned from "show bgp neighbor" output, especially since BGP
performs "graceful shutdown" via notification messages under normal
conditions
I.e., you should probably be very concerned with any session
reset for which no valid explanation is available via CLI or
other means.
-danny
