From: Eldad Zack <eldad@stoneshaft.ath.cx>
To: Kurt Lieber <klieber@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] locking user accounts doesn't really lock them.
Date: Sat, 1 Nov 2003 13:50:14 +0200 (IST) [thread overview]
Message-ID: <Pine.LNX.4.58.0311011345170.2064@localhost> (raw)
In-Reply-To: <20031031220111.GA2395@mail.lieber.org>
On Fri, 31 Oct 2003, Kurt Lieber wrote:
> On Fri, Oct 31, 2003 at 01:55:13PM -0800 or thereabouts, Kevyn Shortell wrote:
> > It's often overlooked but a much easier method for locking a user out is
> > simply to change their default shell to /bin/false or something like it.
> > SSH keys or not, they won't be getting access to the box anytime soon
> > without a default shell.
>
> A valid point, but iirc, this still allows the user to do things which
> don't require an interactive shell. (scp, for instance)
I don't think that is the case - actually, I've managed to break scp by
changing bashrc output.
scp does require the user to have a valid shell.
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2003-11-01 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-31 21:27 [gentoo-dev] locking user accounts doesn't really lock them Kurt Lieber
2003-10-31 21:55 ` Kevyn Shortell
2003-10-31 22:01 ` Kurt Lieber
2003-10-31 22:18 ` Kurt Lieber
2003-11-01 2:47 ` Lisa Seelye
2003-11-01 11:50 ` Eldad Zack [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.58.0311011345170.2064@localhost \
--to=eldad@stoneshaft.ath.cx \
--cc=gentoo-dev@gentoo.org \
--cc=klieber@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox