[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Prefix hijacking, how to prevent and fix currently

Subject: Prefix hijacking, how to prevent and fix currently
From: karsten_thomann at linfre.de (Karsten Thomann)
Date: Fri, 29 Aug 2014 11:43:39 +0200
In-reply-to: <m27g1r8wiz.wl%[email protected]>
References: <CAAjbWEr_o+yQY1T72JMvJ_Nw2Eu2L7=TzZ0dc33mhodo5JB=yw@mail.gmail.com> <[email protected]> <[email protected]> <m2egvz8x6r.wl%[email protected]> <[email protected]> <m27g1r8wiz.wl%[email protected]>

Am 29.08.2014 11:39, schrieb Randy Bush:
>>>> Loose mode would drop failing routes, iff there is covering (i.e. less
>>>> specific is ok) route already in RIB.
>>> isn't that exactly the hole punching attack?
>> No, as the the more specific route is signed and is preferred (longest
>> match routing) against the less specific hijacked route
> clearly i am missing something.  got a write-up?
>
> randy
sorry my mistake, you're right

Follow-Ups:
- Prefix hijacking, how to prevent and fix currently
  - From: randy at psg.com (Randy Bush)

References:
- Prefix hijacking, how to prevent and fix currently
  - From: lists at tarundua.net (Tarun Dua)
- Prefix hijacking, how to prevent and fix currently
  - From: fred at cisco.com (Fred Baker (fred))
- Prefix hijacking, how to prevent and fix currently
  - From: saku at ytti.fi (Saku Ytti)
- Prefix hijacking, how to prevent and fix currently
  - From: randy at psg.com (Randy Bush)
- Prefix hijacking, how to prevent and fix currently
  - From: karsten_thomann at linfre.de (Karsten Thomann)
- Prefix hijacking, how to prevent and fix currently
  - From: randy at psg.com (Randy Bush)

Prev by Date: Prefix hijacking, how to prevent and fix currently
Next by Date: Prefix hijacking, how to prevent and fix currently
Previous by thread: Prefix hijacking, how to prevent and fix currently
Next by thread: Prefix hijacking, how to prevent and fix currently
Index(es):
- Date
- Thread