Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!sdd.hp.com!spool.mu.edu!uunet!mcsun!hp4nl!svin02!svbs01!wswietse
From: wswietse@svbs01.bs.win.tue.nl (Wietse Venema)
Newsgroups: comp.unix.misc
Subject: Re: who's fingering me
Keywords: finger
Message-ID: <2025@svin02.info.win.tue.nl>
Date: 27 Jun 91 15:31:59 GMT
References: <noamb.676562323@over> <1991Jun10.155314.4829@ms.uky.edu> <rcbarn.676630997@rwa.urc.tue.nl> <1991Jun17.163240.19133@sci34hub.sci.com>
Sender: news@svin02.info.win.tue.nl
Reply-To: wswietse@bs.win.tue.nl
Distribution: comp
Lines: 10

>=As a very simple but useful workaround in this case, you can use a 
>=fingerd that immediately fingers back to the host it receives a request 
>=from, thus revealing potential userid of people who are fingering your
>=system. Have a look at ftp.win.tue.nl:~ftp/pub/logdaemon.tar.Z
>=(available for anon. ftp). It contains various utilities of this
>=kind written by Wietse Venema.

Correction: this archive only contains programs that report the remote
host name (and user name in case of rlogin/rsh connections). There are
just too many potential problems with automatic backfingering.