Date: Thu, 14 Feb 2008 09:01:08 -0600 From: Derek Ragona <derek@computinginnovations.com> To: Alex Zbyslaw <xfb52@dial.pipex.com>, freebsd-questions@freebsd.org Subject: Re: Help with su on 6.3 Message-ID: <6.0.0.22.2.20080214085041.02438ce8@mail.computinginnovations.com> In-Reply-To: <47B44D25.10804@dial.pipex.com> References: <bd20341a0802121616k51de1330g4bc486072a4c097b@mail.gmail.com> <6.0.0.22.2.20080212190133.024c3008@mail.computinginnovations.com> <bd20341a0802131051h4d5e2680tc8aa52f644c56ef8@mail.gmail.com> <6.0.0.22.2.20080213125757.02532c58@mail.computinginnovations.com> <47B44D25.10804@dial.pipex.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 08:16 AM 2/14/2008, Alex Zbyslaw wrote:
>Derek Ragona wrote:
>
>>I usually just set the shell to /usr/bin/false or /usr/sbin/nologin for
>>users like these. Of course you can't test these interactively with
>>su. If you want to do that, give the account a valid login shell, test
>>it, then set it to false or nologin.
>It's not clear to me what you mean by "you can't test these interactively
>with su". If you mean you can't su to them and get a shell; that's wrong.
>
>su -m account_with_fake_shell
>
>--Alex
Alex,
What I meant to say was that you can:
su -m account_with_fake_shell
But you can't:
su - account_with_fake_shell
and then test any command and scripts in the user's environment.
-Derek
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.0.0.22.2.20080214085041.02438ce8>