Date: 6 Aug 1997 19:56:07 GMT From: doka@dragon.opera.kharkov.ua (Vladimir Litovka) To: freebsd-security@freebsd.org Subject: SUMMARY: identd working? Message-ID: <5saksn$ln5$1@grunt.vl.kharkov.ua>
next in thread | raw e-mail | index | archive | help
Hello!
On Wed, 6 Aug 1997, Hoss Firooznia wrote:
> > On my system (FreeBSD 2.2.2) don't work identd (pident-2.2.4) I have such
> > line in inetd.conf:
> >
> > ident stream tcp wait root /usr/local/sbin/identd identd -w -t120
> >
> > but when connecting to remote side, there is no identification.
>
> It's possible (but probably unlikely) that your system has been broken
> into and your copy of identd has been replaced with a "trojan horse"
> program that allows attackers back into your system.
I don't think such, because I recently rebuild pident package, and problem
is still. This feature happens only with some versions of inetd. For
example, inetd, that is in FreeBSD package, work normally. So, this isn't
a problem of pidentd, but IMHO problem of inetd.
> Below I've included a recent CERT advisory that explains the problem.
> Good luck, and I hope this is just a harmless problem with identd and
> not something more serious.
Thank you. I _think_ that there isn't hacker's wars :-)
Vladimir Litovka <doka@kharkiv.net>, UNIX System Administrator
Check my resume at http://pasha.tnp.com/~doka
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~NewsGate~ (c) Vladimir Litovka <doka@kharkiv.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5saksn$ln5$1>