From owner-freebsd-isp Fri Jan 7 6:27:51 2000 Delivered-To: freebsd-isp@freebsd.org Received: from federation.addy.com (federation.addy.com [208.11.142.20]) by hub.freebsd.org (Postfix) with ESMTP id D7895156A2 for ; Fri, 7 Jan 2000 06:27:47 -0800 (PST) (envelope-from jim@federation.addy.com) Received: from localhost (jim@localhost) by federation.addy.com (8.9.3/8.9.3) with ESMTP id JAA12064; Fri, 7 Jan 2000 09:27:40 -0500 (EST) (envelope-from jim@federation.addy.com) Date: Fri, 7 Jan 2000 09:27:40 -0500 (EST) From: Jim Sander To: Mike Fisher Cc: freebsd-isp@FreeBSD.ORG Subject: Re: MUA as shell for mail-only accounts? 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 > SSH RSA Authentication If a user who's shell is set to pine has been *'d out, even if he uses RSA Auth to log in they will still be restricted to pine as well as any other email-only user. Of course this problem is another entire issue. > A (theoretical) way of getting around the shell issue is > ~/.login_conf. From the man page: > shell prog Session shell to execute Also from the man page, talking about ~/.login_conf: " Only a subset of login capabilities may be overridden, typically those which do not involve authentication, resource limits and accounting." I would hope that whoever implemented this system would understand that a user-controlled directory is probably not an appropriate place to allow shell changes. -=Jim=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message