From owner-freebsd-isp Fri Aug 23 10:35:18 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA16301 for isp-outgoing; Fri, 23 Aug 1996 10:35:18 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA16293 for ; Fri, 23 Aug 1996 10:35:15 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id MAA26728; Fri, 23 Aug 1996 12:34:42 -0500 From: Joe Greco Message-Id: <199608231734.MAA26728@brasil.moneng.mei.com> Subject: Re: suid login To: jw@ns.calyx.com (John Williams) Date: Fri, 23 Aug 1996 12:34:41 -0500 (CDT) Cc: freebsd-isp@freebsd.org In-Reply-To: from "John Williams" at Aug 23, 96 02:44:19 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hi, I'm having annoying problems with users who connect, then run login to > hide their source host. My problem isn't so much the (attempted) hiding, > but the fact that after a lot of this activity my w display gets full of > broken fixed entries from people long logged off. Really? I am a little suprised, I usually don't ever see problems with this under FreeBSD. > If I remove the setuid > bit from login can I expect any ill behavior from it other then the fact > that users can no longer re-login without reconnecting? I have noticed > that setuid screen when called with -ln causes similar problems. What is > going on and is there a way I can support those programs without getting > bogus login entries? Well you seem to be having an interesting problem of some sort... A simpler idea for login is simply to chgrp it to the group you use for your users and then chmod g-x it :-) Nasty nasty.. but potentially effective. More interesting would be to figure out what is causing your problems to begin with. ... JG