Package: debsecan Version: 0.4.16+nmu1 Followup-For: Bug #703998 Control: severity -1 important
Hi, please treat this with higher priority. False positives make security reports useless, because it trains the sysop to ignore the report. We cannot only look at the version, since fixes are sometimes backported. However, if the user has set the suite, we can know the version *for each suite* where the unfixed->fixed transition takes place. X -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages debsecan depends on: ii debconf [debconf-2.0] 1.5.52 ii python 2.7.5-5 ii python-apt 0.9.3.1 Versions of packages debsecan recommends: ii cron 3.0pl1-124 ii exim4 4.82-5 ii exim4-daemon-light [mail-transport-agent] 4.82-5 debsecan suggests no packages. -- debconf information: * debsecan/suite: sid * debsecan/source: * debsecan/report: true * debsecan/mailto: root -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
