From owner-freebsd-isp Mon Jul 13 21:09:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA12997 for freebsd-isp-outgoing; Mon, 13 Jul 1998 21:09:19 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from rheingold.reed.edu (wcooley@c029h021.ipdorm.reed.edu [134.10.29.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA12992 for ; Mon, 13 Jul 1998 21:09:17 -0700 (PDT) (envelope-from wcooley@nakedape.ml.org) Received: from localhost (wcooley@localhost) by rheingold.reed.edu (8.9.0/8.9.0) with SMTP id VAA32621 for ; Mon, 13 Jul 1998 21:08:50 -0700 Date: Mon, 13 Jul 1998 21:08:50 -0700 (PDT) From: "W. Reilly Cooley, Esq." X-Sender: wcooley@rheingold To: freebsd-isp@FreeBSD.ORG Subject: /usr/bin/passwd bad for shell? 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 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 them an easy way to change their passwords. I'm too paranoid to use a web-based password changer. What about a shell script that printed some information and then ran passwd? Wil -- W. Reilly Cooley Linux 2.0.34 Naked Ape Consulting FreeBSD 2.2.6 wcooley@nakedape.ml.org NetBSD/sun3 1.3.2 http://www.nakedape.ml.org NetBSD/pmax 1.3.2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message