Package: caudium Version: 2:1.2.35-1 Severity: normal After dist-upgrades on several systems, Caudium all of a sudden was installed (I never asked for it and didn't even know what it was). That isn't a problem in and of itself, I suppose, if the Debian maintainers consider it important enough (although I seriously doubt a lot of people are using it).
What is a problem is that Caudium was started at boot time on port 80 and prevented Apache from running. Worse yet, Caudium's default configuration seems to be such that it exposes the source for PHP scripts. And because Caudium serves normal web pages from the normal places, one doesn't even immediately notice this problem. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.9-1-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages caudium depends on: ii caudium-modules 2:1.2.35-1 C modules for Caudium ii debconf 1.4.45 Debian configuration management sy ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii pike7.2 7.2.580-3 Powerful interpreted programming l ii pike7.2-crypto 7.2.580-3 Crypto module for Pike ii pike7.2-gz 7.2.580-3 Gz module for Pike ii pike7.2-image 7.2.580-3 Image module for Pike -- debconf information: * caudium/start_options: threads caudium/cfg_port_taken: * caudium/config_port: 22202 caudium/experimental_http: false caudium/config_password_mismatch: * caudium/config_login: admin * caudium/config_password_reset: * caudium/performance: false * caudium/listen_on: 80 * caudium/last_screen: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
