Package: sysklogd Version: 1.4.1-20 Followup-For: Bug #273269
Please consider changing the severity of this bugreport. There is a remote bug that can freeze the system when using -r: To reproduce it: * Set as nameserver 127.0.0.1 * Start syslogd with -r * Have a remote system log messages (1 per 2-3 seconds is enough) * Start a local named (this will freeze) * Try to login This will freeze the system because syslogd uses gethostbyname() to do the lookups which blocks it. Bind has already binded at port 53 but is not able to perform lookups yet since it waits for some messages to be logged to the syslog. syslog keeps trying to resolve the remote hostname and still gets messages from it. Sending spoofed syslog packets amy keep the system from actually booting. There is no need to use a local named for it. When using a remote nameserver that is not responding, syslog will be blocked. A blocked syslogd results in blocking all processes that try to log something. su, login, etc, all try to log something and thus you're not able to login to the system until about 30 seconds have passed. At least add a note to the /etc/default/sysklogd script to warn users that when using -r they should have the appropriate entries in /etc/hosts. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable'), (150, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.22-v2-v (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages sysklogd depends on: ii klogd [linux-kernel-log-daemo 1.4.1-20 Kernel Logging Daemon ii libc6 2.5-9+b1 GNU C Library: Shared libraries sysklogd recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
