Merit Network
Can't find what you're looking for? Search the Mail Archives.
  About Merit   Services   Network   Resources & Support   Network Research   News   Events   Home

Discussion Communities: Merit Network Email List Archives

North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: That pesky AS path corruption bug...

  • From: John Fraizer
  • Date: Wed May 24 00:36:47 2000

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. :-P
> 
> You 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









Discussion Communities


About Merit | Services | Network | Resources & Support | Network Research
News | Events | Contact | Site Map | Merit Network Home


Merit Network, Inc.