Date: Tue, 1 Aug 2000 10:42:58 -0500 (CDT) From: James Wyatt <jwyatt@rwsystems.net> To: Randall Gellens <randy@qualcomm.com> Cc: freebsd-isp@freebsd.org, freebsd-questions@freebsd.org Subject: RE: How can I disable FreeBsd Users Message-ID: <Pine.BSF.4.10.10008011041380.81070-100000@bsdie.rwsystems.net> In-Reply-To: <p05000809b5ac8db32d44@[10.81.78.127]>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.10008011041380.81070-100000>