Package: debsecan Version: 0.4.9 Severity: wishlist Hi,
I have a low-memory host A which has its filesystem rsynced from a "golden chroot" from another host B. Both copies of the filesystem run cron, and therefore debsecan. When debsecan runs in the chroot on B, it gets the subject "Debian security status of B", when it is already the status of A. I'd like to be able to change the subject from /etc/default, but it looks like the subject is harcoded in debsecan's code. Greetings Marc -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.22.1-scyw00225 (PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages debsecan depends on: ii debconf [debconf-2.0] 1.5.14 Debian configuration management sy ii python 2.4.4-6 An interactive high-level object-o ii python-apt 0.7.3.1 Python interface to libapt-pkg Versions of packages debsecan recommends: ii cron 3.0pl1-100 management of regular background p ii exim4-daemon-heavy [mail-tran 4.67-7 Exim MTA (v4) daemon with extended -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
