[70018] in North American Network Operators' Group
RE: Juniper failes to change keys (More MD5 fun: Cisco uses wrong
daemon@ATHENA.MIT.EDU (Christopher L. Morrow)
Sun Apr 25 16:41:17 2004
Date: Sun, 25 Apr 2004 20:40:06 +0000 (GMT)
From: "Christopher L. Morrow" <christopher.morrow@mci.com>
To: "Malayter, Christopher" <Christopher.Malayter@tdstelecom.com>
Cc: "'nanog@merit.edu'" <nanog@merit.edu>
In-Reply-To: <7F14AEA6809DD511BA1B00508BBE584E05A7824A@msg017.teldta.com>
Errors-To: owner-nanog-outgoing@merit.edu
On Sun, 25 Apr 2004, Malayter, Christopher wrote:
>
> I agree here. If we can roll new md5 keys without session resets I am all
> for it. I believe Juniper needs to fix their implementation. Especially
> with md5 rolling out network wide for quite a few networks. If an employee
I'd point out that this headache is likely why MANY networks didn't deploy
md5 before last week, or perhaps haven't even deployed it to date...
