Date: Mon, 12 Mar 2012 15:47:59 -0700 From: "Edward M." <eam1edward@gmail.com> To: Polytropon <freebsd@edvax.de> Cc: freebsd-questions@freebsd.org Subject: Re: Editor With NO Shell Access? Message-ID: <4F5E7D1F.9030703@gmail.com> In-Reply-To: <20120312232300.4da8ebf3.freebsd@edvax.de> References: <4F5E4C2A.1020005@tundraware.com> <4F5E6D3A.50302@gmail.com> <20120312231000.4bb530e1.freebsd@edvax.de> <4F5E7687.5070808@gmail.com> <20120312232300.4da8ebf3.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/12/2012 03: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.
>
>
>
Now i gotta try this out. Off to
hosed my system.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F5E7D1F.9030703>