Package: debsecan Version: 0.4.10+nmu1 Followup-For: Bug #463176 in regard to this bug, i think that the debsecan data is out of sync with the security tracker. if you look at [1], you will not see CVE-2005-3625 listed in the issues affecting stable. however, for some reason debsecan disagrees, and says that it does apply to etch.
this should be an easy fix. thanks for the hard work. [1] http://security-tracker.debian.net/tracker/status/release/stable -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.18-6-686 (SMP w/1 CPU core) 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 debsecan depends on: ii debconf [debconf-2.0] 1.5.21 Debian configuration management sy ii python 2.5.2-1 An interactive high-level object-o ii python-apt 0.7.5 Python interface to libapt-pkg Versions of packages debsecan recommends: ii cron 3.0pl1-104 management of regular background p pn exim4 | mail-transport-agent <none> (no description available) -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
