If the DHCP options are stored in a DHCP-specific config somewhere, and if your app has to fetch the options from that config in order to use them, then this kind of thing is not only harmless but is also pretty handy, since you can provide a user-config option that asks if they want to use DHCP or not. If so, fetch the data.
If the DHCP client tries to update application-configuration data files directly (pushing the DHCP options out to your app), then this also means that somebody has modified the machine-wide DHCP client configuration with the path information to your app config file, meaning that somebody with privileges wants this to happen. If you use something like a DHCP mini-config file that the admin can point to, then you can also give the current user an option of using DHCP or some other configuration mechanism with a basic config option. -- Eric A. Hall http://www.ehsco.com/ Internet Core Protocols http://www.oreilly.com/catalog/coreprot/
