|
From: Heiko Z. <he...@zu...> - 2007-03-13 17:52:20
|
On Tue, March 13, 2007 12:45, Philip Peake wrote: > One other item I noticed. > I use a different firewall than the ones provided (don't know if this > matters here). > > When networking is started, network communications are blocked (all > packets dropped). Starting up the firewall opens up the network (as much as > the firewall allows). This is fine, since it closes a security hole during > boot. > > However, syslog is started BEFORE the firewall is brought up. If you are > logging to a remote system, it, of course, fails since it can't connect. > The workaround for that is to change the order of startup to have syslog > start after the firewall is set up. I'm fine with doing this change if nobody else has a complain about it. -- Regards Heiko Zuerker http://www.devil-linux.org |