Date: Tue, 20 Apr 1999 10:55:23 -0400 (EDT) From: David Gilbert <dgilbert@velocet.ca> To: "Harry M. Leitzell" <Harry_M_Leitzell@cmu.edu> Cc: "Frederick J Polsky v1.0" <fred@fredbox.com>, security@FreeBSD.ORG Subject: Re: poink attack (was Re: ARP problem in Windows9X/NT) Message-ID: <14108.38235.254919.924353@trooper.velocet.ca> In-Reply-To: <Pine.LNX.3.96L.990419222013.8966A-100000@unix48.andrew.cmu.edu> References: <Pine.BSF.4.05.9904191804230.13349-100000@bogomatic.fredbox.com> <Pine.LNX.3.96L.990419222013.8966A-100000@unix48.andrew.cmu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "Harry" == Harry M Leitzell <Harry_M_Leitzell@cmu.edu> writes: Harry> It also hits college campuses, which are a haven for Harry> misconfigured Linux machines that provide easy quick root Harry> access on the Local network. Not to say that CMU has this Harry> problem or anything like that. Not this discussion 'should' be about what 'should' be, but wouldn't it make sense to have the DHCP server be the 'athority' by which hardware addresses are resolved? I suppose there's little security built into that protocol, too. We recently went to implement it for a customer and were somewhat taken aback by what could happen if someone managed to just 'connect' a laptop to the network who wasn't supposed to. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14108.38235.254919.924353>