IETF Logo Mail Archive

Re: Security hole in RIP-2

Noel Chiappa <jnc@ginger.lcs.mit.edu> Thu, 04 February 1993 16:37 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06378; 4 Feb 93 11:37 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa06372; 4 Feb 93 11:37 EST
Received: from atlas.xylogics.com by CNRI.Reston.VA.US id aa12209; 4 Feb 93 11:37 EST
Received: by atlas.xylogics.com id AA25440 (5.65c/UK-2.1-930202); Thu, 4 Feb 1993 11:41:10 -0500
Received: from GINGER.LCS.MIT.EDU by atlas.xylogics.com with SMTP id AA17640 (5.65c/UK-2.1-930202); Thu, 4 Feb 1993 11:40:56 -0500
Received: by ginger.lcs.mit.edu id AA18906; Thu, 4 Feb 93 11:36:02 -0500
Date: Thu, 04 Feb 1993 11:36:02 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Noel Chiappa <jnc@ginger.lcs.mit.edu>
Message-Id: <9302041636.AA18906@ginger.lcs.mit.edu>
To: gmalkin@xylogics.com, ietf-rip@xylogics.com
Subject: Re: Security hole in RIP-2
Cc: jnc@ginger.lcs.mit.edu

	This is of course only true for the simple password scheme. A more
secure system (e.g. with a hidden key as part fo a checksum) would be
immune. Still, the change you suggest is a good one.

	Noel

v2.23.0 | Report a Bug | By Email