On Wed, 2008-10-29 at 02:01 -0400, Peter Memishian wrote:
> > > Perhaps I'm misunderstanding part of the proposal, but having hardcoded
> > > policy in applications that cannot be overridden (e.g., by an admin who
> > > never wants to let DHCP through for a certain environment) seems bad.
> >
> > This would be a misconfigured system.
>
> I'm not sure I follow what you're saying, so let me try a different way of
> asking my question. Suppose I'm an admin and I want to lock down the
> system such that it send or receive DHCP, period. Now suppose something
> on the system (e.g., NWAM) decides to start up DHCP, and I'm unaware of
> this. Will my wishes be honored or not?
You might as well ask if a system administered by two people who never
talk to each other will be secure. (It won't be). We cannot produce
psychic software which reads the mind of a system administrator.
Software which runs as a privileged user must be properly configured.
Positing that an administrator would intend to use DHCP to configure an
interface *and* intend to block all DHCP traffic is nonsensical.
- Bill
