Date: Fri, 12 May 1995 16:03:08 -0700 (PDT) From: Poul-Henning Kamp <phk@ref.tfs.com> To: henrich@crh.cl.msu.edu (Charles Henrich) Cc: freebsd-hackers@FreeBSD.org Subject: Re: REMOTE_HOST & REMOTE_USER Message-ID: <199505122303.QAA06040@ref.tfs.com> In-Reply-To: <199505122232.PAA11874@freefall.cdrom.com> from "Charles Henrich" at May 12, 95 06:32:08 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> How do you folks feel about making inetd set the REMOTE_HOST variable to the > hostname/ip of the connected peer? SGI's do this and it comes in quite handy. > > Is inetd the right place (instead of login say?). I keep debating between the > two, but for maximal benefit I think it should stay in inetd, and have login > preserve the value, or reset it.. Good idea. Consider two variables: REMOTE_IP=192.168.1.3 REMOTE_PORT=2345 -- Poul-Henning Kamp <phk@login.dknet.dk> -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant'
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505122303.QAA06040>