I had the very same thoughts, being a university you can imagine what
physical security is like, plus management wants to give students the
ability to walk on campus and plugin, plus start wireless services too.

>From what people have sent back from my question, I don;t think we will be
any worse of security wise as far as moving to DHCP will go.

Thanks for the various responses, if someone still thinks of a big issue I
would love to hear it.

Cheers,

Stewart

On Tue, 29 Oct 2002, Jones, Steven wrote:

> Date: Tue, 29 Oct 2002 12:19:06 +1300
> From: "Jones, Steven" <[EMAIL PROTECTED]>
> To: 'Stewart James' <[EMAIL PROTECTED]>,
>      debian-security@lists.debian.org
> Subject: RE: DHCP
> Resent-Date: Mon, 28 Oct 2002 17:24:16 -0600 (CST)
> Resent-From: debian-security@lists.debian.org
>
> u could set dhcp to give out a fixed address dependant on a mac address,
> this would stop just anybody plugging a box into a network, if your network
> is physically secure then thats not a worry. (a cat5 jack in reception or
> some other public place is dodgy)
>
> Otherwise dhcp makes life easier...its the only way to manage a decent sized
> network.
>
> :)
>
> Steven
>
> -----Original Message-----
> From: Stewart James [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 29 October 2002 12:03
> To: debian-security@lists.debian.org
> Subject: DHCP
>
>
>
> I was hoping someone could help me out here. Currently I am still on a
> netowrk using static IP configurationon each machine, we are finally
> moving towards DHCP. Are there any security considerations to be made to
> ensure there is no gapping security hole. the various howto's I have seen
> don;t seem to have a clear "Security" section and I havent seen it
> mentioned in any of the faq's
>
> Thanks for any assistance,
>
> Stewart James
>
>
>

Reply via email to