chkrootkit (0.59-1) unstable; urgency=medium

  The 0.59 version of chkrootkit introduces a check for processes running
  from memory: this is very preliminary code, and you should not rely on
  this to detect anything: instead, you can use the checkrestart(1)
  command from the 'debian-goodies' package for a more comprehensive check
  of processes using deleted files.

  The upstream version of chkrootkit introduced an (undocumented) option
  '-s' to check that needed commands are available. This clashes with a
  patch that has been in Debian since (at least) 2010 which added -s as an
  option (to filter the output from the 'sniffer' test). The upstream
  option has been renamed to '--selfcheck' in Debian.

 -- Richard Lewis <richard.lewis.debian@googlemail.com>  Sat, 18 Apr 2025 11:30:00 +0100

chkrootkit (0.57-2) unstable; urgency=medium

  The Debian version of chkrootkit disbles two tests that
  involve sending kill signals to processes:

  * The test for 'Kovid LKM' sends a 'SIGCONT' to pid 31337
  * The test for 'ENYELKM LKM' sends various signals to pids 12345 and 1

  These tests have been disabled because if those pids are regular processes the
  signal may cause undesirable consequences.

  This means that chkrootkit will potentially fail to detect these rootkits.

 -- Richard Lewis <richard.lewis.debian@googlemail.com>  Sun, 12 Mar 2023 12:31:00 +0100