From owner-freebsd-questions@FreeBSD.ORG Tue Mar 13 15:43:32 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 84FC5106564A for ; Tue, 13 Mar 2012 15:43:32 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from ozzie.tundraware.com (ozzie.tundraware.com [75.145.138.73]) by mx1.freebsd.org (Postfix) with ESMTP id 2B8C38FC22 for ; Tue, 13 Mar 2012 15:43:31 +0000 (UTC) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.5/8.14.5) with ESMTP id q2DFhN1M078709 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Tue, 13 Mar 2012 10:43:23 -0500 (CDT) (envelope-from tundra@tundraware.com) Message-ID: <4F5F6B1A.7070808@tundraware.com> Date: Tue, 13 Mar 2012 10:43:22 -0500 From: Tim Daneliuk User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: FreeBSD Mailing List References: <4F5E4C2A.1020005@tundraware.com> <4F5E6D3A.50302@gmail.com> <20120312231000.4bb530e1.freebsd@edvax.de> <4F5E7687.5070808@gmail.com> <20120312232300.4da8ebf3.freebsd@edvax.de> <4F5EEBB4.1080608@gmail.com> In-Reply-To: <4F5EEBB4.1080608@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (ozzie.tundraware.com [192.168.0.1]); Tue, 13 Mar 2012 10:43:23 -0500 (CDT) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: q2DFhN1M078709 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No Subject: Re: Editor With NO Shell Access? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2012 15:43:32 -0000 On 03/13/2012 01:39 AM, Joshua Isom wrote: > On 3/12/2012 5:23 PM, Polytropon wrote: >> On Mon, 12 Mar 2012 15:19:51 -0700, Edward M. wrote: >>> On 03/12/2012 03:10 PM, Polytropon wrote: >>>> /etc/shells to work, but a passwd entry like >>>> >>>> bob:*:1234:1234:Two-loop-Bob:/home/bob:/usr/local/bin/joe >>> >>> >>> I think this would not let the user to login,etc >> >> I'm not sure... I assume logging in is handled by /usr/bin/login, >> and control is then (i. e. after successful login) transferred >> to the login shell, which is the program specified in the >> "shell" field (see "man 5 passwd") of /etc/passwd. How is >> login supposed to know if the program specified in this >> field is actually a dialog shell? >> >>> From "man 1 login" I read that many shells have a built-in >> login command, but /usr/bin/login is the system's default >> binary for this purpose if the "shell" (quotes deserved if >> it is an editor as shown in my assumption) has no capability >> of performing a login. >> >> >> > > Are they logging in from the console or from ssh? If it's from a console, I'd send them directly into a jail with limited file system access, so that excecutables don't matter. If it's from ssh, I'd do the same thing. > > Assume they can break out of the editor or that something will happen. Make it minimalist about what they can do. Use the /rescue/vi in an empty jail with the files available. Don't think about changing editors, change the system. That's a really good idea, but we're talking about almost 1000 systems here. That's a whole bunch of configuration... -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/