From owner-freebsd-isp Tue Jul 14 18:37:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22350 for freebsd-isp-outgoing; Tue, 14 Jul 1998 18:37:19 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from trantor.galaxia.com (terminus.galaxia.com [204.255.210.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22338 for ; Tue, 14 Jul 1998 18:37:14 -0700 (PDT) (envelope-from dave@galaxia.com) Received: from localhost (dave@localhost) by trantor.galaxia.com (8.8.8/8.8.7) with SMTP id VAA17607; Tue, 14 Jul 1998 21:36:51 -0400 (EDT) (envelope-from dave@galaxia.com) Date: Tue, 14 Jul 1998 21:36:51 -0400 (EDT) From: "David H. Brierley" To: "W. Reilly Cooley, Esq." cc: freebsd-isp@FreeBSD.ORG Subject: Re: /usr/bin/passwd bad for shell? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 13 Jul 1998, W. Reilly Cooley, Esq. wrote: > Would it be dangerous to use /usr/bin/passwd as a shell for users? I would > prefer not to give interactive shells by default, but would like to give I use the passwd program as a shell for non-interactive users all the time and it works quite nicely. It prevents them from logging in but allows them to change their password without having to call your tech support dept. If they will be using ftp to transfer files to your server (i.e. for web pages), make sure the passwd program is listed in the /etc/shells file. -- David H. Brierley dave@galaxia.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message