From: Borsenkow Andrej <Andrej.Borsenkow@mow.siemens.ru>
To: Emre Yildirim <emre@asper.org>
Cc: zsh-users@sunsite.dk
Subject: Re: restricted shell
Date: 21 Oct 2001 23:00:49 +0400 [thread overview]
Message-ID: <1003690856.3370.17.camel@localhost.localdomain> (raw)
In-Reply-To: <3BD314E4.8090802@sgi.asper.org>
On Вск, 2001-10-21 at 22:33, Emre Yildirim wrote:
> Ooops, Sorry I was reading the man page, and right after I sent this
> email, I saw the restricted shell section. I have another question:
>
> When I setup a restricted shell for a user, and let's say I put
> PATH=/r in his .zprofile and /r contains no binaries, he is still
> able to execute certain commands (like echo, pwd, export, etc).
> How can I restrict the execution of those commands as well?
>
Using disable builtin. Make .zshrc read-only for user (or do it in
system zshrc and make user's home directory read-only) and put
disable echo
there.
> Also there are programs like pine that allow users to break out of
> restricted shells. Any tips on how to limit that as well?
>
Do not allow user to run them :-) Really, that is everything you can do
- examine every program for possible back-doors before allowing
restricted users to execute them.
Pine allows you to have system-wide config file that takes precedence
over any user settings. Vim has restricted mode as well IIRC
-andrej
next prev parent reply other threads:[~2001-10-21 19:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-21 18:09 Emre Yildirim
2001-10-21 18:16 ` Mads Martin Joergensen
2001-10-21 18:33 ` Emre Yildirim
2001-10-21 19:00 ` Borsenkow Andrej [this message]
2001-10-21 19:12 ` Emre Yildirim
2001-10-21 19:21 ` Nadav Har'El
2001-10-21 19:32 ` Emre Yildirim
2001-10-21 19:53 ` Bart Schaefer
2001-10-21 20:10 ` Emre Yildirim
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=1003690856.3370.17.camel@localhost.localdomain \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=emre@asper.org \
--cc=zsh-users@sunsite.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).