Now, maybe I am too innocent, but believe Kevin's original mail does cover the
vulnerability. As far as I can see both filters below would stop the
vulnerability. There is not the functionality of blocking Type 0, Type 1 or
Type 2, but supposely any of them is either not used or dangerous.
fi
> Date: Tue, 24 Apr 2007 16:46:30 +0300 (EEST)
> From: Pekka Savola <[EMAIL PROTECTED]>
>
> On Tue, 24 Apr 2007, Kevin Oberman wrote:
> >> Kevin,
> >>
> >> Slide 20 of the presentation states that RH processing can not be
> >> deavtivat> ed on Juniper routers. Not sure whether that applies to
> >>
On Tue, 24 Apr 2007, Kevin Oberman wrote:
>> Kevin,
>>
>> Slide 20 of the presentation states that RH processing can not be
>> deavtivat> ed on Juniper routers. Not sure whether that applies to
>> JunOS, JunosE or bo> th.
>>
>> Cheers,
>
> The issue is the RH0 header. RH2 is not a problem and is es
> Date: Tue, 24 Apr 2007 03:09:07 + (GMT)
> From: [EMAIL PROTECTED]
> Sender: [EMAIL PROTECTED]
>
> Kevin,
>
> Slide 20 of the presentation states that RH processing can not be
> deavtivat> ed on Juniper routers. Not sure whether that applies to
> JunOS, JunosE or bo> th.
>
> Cheers,
The is
4 matches
Mail list logo