From owner-freebsd-commit Thu Nov 2 11:46:20 1995 Return-Path: owner-commit Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA13045 for freebsd-commit-outgoing; Thu, 2 Nov 1995 11:46:20 -0800 Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA13033 for cvs-all-outgoing; Thu, 2 Nov 1995 11:46:17 -0800 Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA13023 for cvs-CVSROOT-outgoing; Thu, 2 Nov 1995 11:46:15 -0800 Received: from jhome.DIALix.COM (root@jhome.DIALix.COM [192.203.228.69]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA13016 ; Thu, 2 Nov 1995 11:45:28 -0800 Received: (from peter@localhost) by jhome.DIALix.COM (8.6.12/8.6.9) id DAA06601; Fri, 3 Nov 1995 03:44:32 +0800 Date: Fri, 3 Nov 1995 03:44:31 +0800 (WST) From: Peter Wemm To: "Jordan K. Hubbard" cc: CVS-commiters@freefall.freebsd.org, cvs-CVSROOT@freefall.freebsd.org Subject: Re: cvs commit: CVSROOT log_accum.pl In-Reply-To: <11794.815338111@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-commit@FreeBSD.org Precedence: bulk On Thu, 2 Nov 1995, Jordan K. Hubbard wrote: > > swallace 95/11/02 01:30:23 > > > > Modified: . log_accum.pl > > Log: > > Take $ENV{'USER'} for the login name, as rshd, telnetd and rlogind all > > set it. I'm still at a loss to explain why getlogin and `logname` > > (which make a supposedly secure system call) are returning somebody else's > > username when cvs (a non privileged process) is run on the end of a rsh. > > If I do: rsh freefall 'print getlogin' it always seems to work... > > > > (If this doesn't work after this commit, I might commandeer Jeffrey Hsu's > > login.. :-) This commit may say 'hsu' though.) > > Nope, now you're Steven Wallace! Peter Wemm, man of a thousand identities! :-) > > Jordan Damn.. I can never keep up these days. First Peter Wemm, then Jeffery Hsu, then I became Dave Tweten, back to Jeffrey Hsu, and now Steven! No wonder I'm having so much trouble.. Jordan :-) :-) :-) (well, at least we've found the problem and can fix it in inetd and the kernel)