On 08 Dec 2004, lantz moore <[EMAIL PROTECTED]> wrote:
> Philipp Weis <[EMAIL PROTECTED]> writes:
>
> > Well, there is something strange going on. This bug appeared after
> > yesterday's daily sid updates, but I have no idea what could have
> > triggered it.
> >
> > So, this is what's happening:
> >
> > | # chkrootkit sshd
> > | ROOTDIR is `/'
> > | Checking `sshd'... /usr/bin/strings: Warning: '/' is not an ordinary
> > | file
> > | not infected
> >
> > The problem seems to be that "getCMD sshd" returns "/" as sshd's
> > command name. getCMD checks some possible locations, the first one
> > beeing "/", because sshd is not running. The -r test in line 1042
> > succeeds, and "/" is returned as the location. If have corrected this
> > error locally with an additional -f test, but I'm not sure this is the
> > way this is supposed to work. Maybe it would be better to examine
> > ${ROOTDIR}${RUNNING} only if ${RUNNING} is non-empty.
>
> is this still occurring?Yes, it is still like this on my system. PS: I did not receive your mail, as you sent this message only to [EMAIL PROTECTED] and not to me as well. -- Philipp Weis [EMAIL PROTECTED] http://pweis.com/
signature.asc
Description: Digital signature
