On Mon, Jul 11, 2011 at 8:48 PM, J Sisson <sisso...@gmail.com> wrote: > On Mon, Jul 11, 2011 at 7:36 PM, Andres Perera <andre...@zoho.com> wrote: >> >> why would you install a daemon and not run it? how is it any different >> than X listening on localhost by default in obsd? if you install a >> daemon in debian/ubuntu and it listens on 0.0.0.0 by default, the >> package isn't following distro policy > > Why would you start a daemon before you have had a chance to > configure it for your environment?B Is it really that hard to run > update-rc.d after you edit a config file?
that wouldn't be any different than sending a HUP signal or restarting through rc.d, assuming listening on localhost is ok. for exceptional situations where it would be not ok, like increasingly rare truly multi-user systems, you can turn it off globally for newly installed packages > > OpenBSD asks if X should run by default when you install the system. > On top of that, the default firewall rules explicitly block traffic to X. > It's quite different in fact. it does not offer granularity covering both "running X" and "X accepting connections from localhost", just like the debian package policy concerning network daemons > > Policy?B Well thank heavens for that...I guess I should run Ubuntu on > all of my critical infrastructure...their policy will protect me.
