From owner-freebsd-questions Tue Aug 1 8:47:59 2000 Delivered-To: freebsd-questions@freebsd.org Received: from bsdie.rwsystems.net (bsdie.rwsystems.net [209.197.223.2]) by hub.freebsd.org (Postfix) with ESMTP id 2A77037BF01; Tue, 1 Aug 2000 08:47:54 -0700 (PDT) (envelope-from jwyatt@rwsystems.net) Received: from bsdie.rwsystems.net([209.197.223.2]) (1658 bytes) by bsdie.rwsystems.net via sendmail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for ; Tue, 1 Aug 2000 10:42:58 -0500 (CDT) (Smail-3.2.0.106 1999-Mar-31 #1 built 1999-Aug-7) Date: Tue, 1 Aug 2000 10:42:58 -0500 (CDT) From: James Wyatt To: Randall Gellens Cc: freebsd-isp@freebsd.org, freebsd-questions@freebsd.org Subject: RE: How can I disable FreeBsd Users In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 Aug 2000, Randall Gellens wrote: > At 9:12 AM +0200 8/1/00, Philipp Gasch=FCtz wrote: > > I think it's far more easy to go via the shell. Have a look into - i > > think - pop_pass.c. There is a function which checks whether the user'= s > > shell is a valid shell. Now, if you are giving all users that you want= to > > disable a shell such as popper.shell (which is a symlink to i.e. bash = or > > false) and you add a couple of lines of code into pop_pass.c where you > > compare the shell retrieved by popper with "popper.shell", you are abl= e > > to lock those out... >=20 > If you want to disable access via the shell, just add '#define > CHECK_SHELL 1' to the top of config.h and recompile Qpopper. If the > user's shell is not valid, the user will be unable to access the > system. If you want to prevent the user from telneting in but still > permit POP access, use a shell value of /POPPER/ANY/SHELL/. Nuts, that's where I put tcsh... 100% (^_^) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message