> > However, NWAM is different, because it's going to invoke DHCP on its
 > > own.  The administrator never really asked.  It's likely that as NWAM
 > > matures, it'll invoke many other things on its own.

Yes, exactly.

 > That's very worrying.
 > 
 > The administrator who cares about security will need either: a) to
 > understand what NWAM is doing or b) be able to disable it.  

With the latter, we'd be back to supporting multiple different network
configuration modes, whereas the hope with NWAM has always been that it'd
evolve to the point where it would be "the" network configuration mode.
Maybe this just means providing an explicit way for the administrator to
control what sort of protocols NWAM uses to get its job done, but to some
degree that seems to fight with the notion of "automagic".  I think this
is (yet another) case where some careful thought is needed to have the
system both end up secure and easy-to-use.

In any case, I disagree with the line of thinking that this just another
case of "dueling admins".

-- 
meem

Reply via email to