zsh-workers
 help / color / mirror / code / Atom feed
From: "Nadav Har'El" <nyh@math.technion.ac.il>
To: Bart Schaefer <schaefer@candle.brasslantern.com>
Cc: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: Enable/disable (was Re: Enhanced shell)
Date: Tue, 24 Jul 2001 01:00:52 +0300	[thread overview]
Message-ID: <20010724010052.A12156@leeor.math.technion.ac.il> (raw)
In-Reply-To: <1010723163850.ZM14004@candle.brasslantern.com>; from schaefer@candle.brasslantern.com on Mon, Jul 23, 2001 at 04:38:50PM +0000

On Mon, Jul 23, 2001, Bart Schaefer wrote about "Enable/disable (was Re: Enhanced shell)":
> } These are useful for restricted-shell mode, when you sometimes want to
> } disable builtins (e.g., the "read" builtin allows the restricted user to
> } read files that they shouldn't).
> 
> As of 4.0.1, `builtin read' will run `read' even after `disable read'.
> Maybe we need to rethink that.

Even if builtin's behavior remains, it's not so terrible, because somebody
who wants to disable a builtin like read will just need to also disable
"builtin", as well as (obviously) the "enable" command (or the restricted user
will be able to reenable the command).

But now that I think of it, does zsh have restricted-shell capabilities at
all? Zsh has been my favorite shell for the last 8 years or so, but when I
needed a restricted shell, I went with pdksh or bash 2. I don't know why...
Perhaps the words "Zsh" and "restricted" just didn't sound right together :)

-- 
Nadav Har'El                        |          Tuesday, Jul 24 2001, 4 Av 5761
nyh@math.technion.ac.il             |-----------------------------------------
Phone: +972-53-245868, ICQ 13349191 |I don't eat snails. I prefer fast food.
http://nadav.harel.org.il           |


  reply	other threads:[~2001-07-23 22:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-22 22:47 Enhanced shell Peter Stephenson
2001-07-23 11:13 ` Oliver Kiddle
2001-07-23 11:38   ` Peter Stephenson
2001-07-23 18:03     ` Bart Schaefer
2001-07-24 13:42       ` Oliver Kiddle
2001-07-23 12:00   ` Nadav Har'El
2001-07-23 16:38     ` Enable/disable (was Re: Enhanced shell) Bart Schaefer
2001-07-23 22:00       ` Nadav Har'El [this message]
2001-07-24  1:12         ` Bart Schaefer
2001-07-24  2:45           ` Here-strings and $functions Bart Schaefer
2001-07-24  6:18             ` Bart Schaefer
2001-07-24  8:12               ` Sven Wischnowsky
2001-07-24 12:16                 ` Bart Schaefer
2001-07-24  9:23         ` Enable/disable (was Re: Enhanced shell) Peter Stephenson
2001-07-24 12:10           ` PATCH: Doc errors (Re: Enable/disable (was Re: Enhanced shell)) Bart Schaefer
2001-07-29  9:53 ` Enhanced shell Zefram
2001-07-29 22:07   ` Peter Stephenson
2001-07-30  1:34     ` Bart Schaefer
2001-07-30  2:19   ` Bart Schaefer

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=20010724010052.A12156@leeor.math.technion.ac.il \
    --to=nyh@math.technion.ac.il \
    --cc=schaefer@candle.brasslantern.com \
    --cc=zsh-workers@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).