Package: checksecurity Version: 2.0.11 Severity: normal Tags: patch The plugin check-sockets does not print anything useful, always gives an empty list of sockets. For me, the following modification fixes the issue:
--- checksecurity_2.0.11_all.deb/usr/share/checksecurity/check-sockets 2008-07-28 00:00:00.000000000 +0200 +++ /usr/share/checksecurity/check-sockets 2009-03-21 17:50:34.000000000 +0100 @@ -75,7 +75,7 @@ # TODO: (jfs) Enhance using netstat if lsof is not available. # use the code @Tiger to do this. -/usr/bin/lsof -i -n -P | egrep 'UDP|TCP.*LISTEN' | egrep -v 'UDP.*->.*' |sed 's/....[0-9]u IP.* / /' | sed 's/ FD TYPE DEVICE SIZE NODE NAME/PROTO PORT/' | sed 's/ [0-9][0-9]* / /'|sed 's/ PID / /'| sed -e 's/[ \t]\+/ /g' | sort -u | >>$TMPSOCKET +/usr/bin/lsof -i -n -P | egrep 'UDP|TCP.*LISTEN' | egrep -v 'UDP.*->.*' |sed 's/....[0-9]u IP.* / /' | sed 's/ FD TYPE DEVICE SIZE NODE NAME/PROTO PORT/' | sed 's/ [0-9][0-9]* / /'|sed 's/ PID / /'| sed -e 's/[ \t]\+/ /g' | sort -u >>$TMPSOCKET set +o noglob if cmp -s sockets.today $TMPSOCKET >/dev/null -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-xen-amd64 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages checksecurity depends on: ii cron 3.0pl1-105 management of regular background p ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii perl 5.10.0-19 Larry Wall's Practical Extraction Versions of packages checksecurity recommends: ii logcheck 1.2.69 mails anomalies in the system logf pn tiger <none> (no description available) pn tripwire | integrit | aide | <none> (no description available) Versions of packages checksecurity suggests: pn apt-watch | cron-apt <none> (no description available) ii lockfile-progs 0.1.11-0.1 Programs for locking and unlocking -- debconf information: checksecurity/oldconf: -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
