nanog mailing list archives
Re: That pesky AS path corruption bug...
From: John Fraizer <nanog () EnterZone Net>
Date: Wed, 24 May 2000 00:33:40 -0400 (EDT)
On 23 May 2000, Sean Donelan wrote:
On Tue, 23 May 2000, Jeff Haas wrote:The only valid defense against such mucking that I can think of is verifying AS adjacencies against some registry and flagging unknown paths. This is not a cheap thing to do. This, however, is far saner than cryptographically signing all routing updates which is one solution I've heard proposed. :-PYou can cryptographically sign bad information as well as good information. Cryptography is good for detecting alterations, not if the information was correct in the first place.
Ahhh... But, if the router is sufficiently confused to be screwing up the update, it will quite possibly be too confused to successfully sign the update and it will fail authentication when the peer receives it. --- John Fraizer EnterZone, Inc
Current thread:
- Re: That pesky AS path corruption bug..., (continued)
- Re: That pesky AS path corruption bug... Vijay Gill (May 23)
- Re: That pesky AS path corruption bug... Vadim Antonov (May 23)
- Re: That pesky AS path corruption bug... Peter T. Whiting (May 23)
- Re: That pesky AS path corruption bug... Vijay Gill (May 23)
- Re: That pesky AS path corruption bug... Blaine Christian (May 23)
- Re: That pesky AS path corruption bug... Vijay Gill (May 23)
- Re: That pesky AS path corruption bug... Jeff Haas (May 23)
- Re: That pesky AS path corruption bug... Vadim Antonov (May 23)
- Re: That pesky AS path corruption bug... Vijay Gill (May 23)
- Re: That pesky AS path corruption bug... Sean Donelan (May 23)
- Re: That pesky AS path corruption bug... John Fraizer (May 23)
- Re: That pesky AS path corruption bug... Adrian Chadd (May 24)
- Re: That pesky AS path corruption bug... Michael Shields (May 24)
- Re: That pesky AS path corruption bug... Adrian Chadd (May 24)
- Re: That pesky AS path corruption bug... John Fraizer (May 23)