zsh-workers
 help / color / mirror / code / Atom feed
From: Hrvoje.Niksic@public.srce.hr (Hrvoje Niksic)
To: A.Main@dcs.warwick.ac.uk (Zefram)
Cc: hzoli@cs.elte.hu, schaefer@nbn.com, A.Main@dcs.warwick.ac.uk,
	zsh-workers@math.gatech.edu
Subject: Re: 8-bit patch for zle_tricky.c
Date: Tue, 21 May 1996 00:43:29 +0200 (MET DST)	[thread overview]
Message-ID: <199605202243.AAA17633@jagor.srce.hr> (raw)
In-Reply-To: <1222.199605202109@stone.dcs.warwick.ac.uk> from Zefram at "May 20, 96 10:09:08 pm"

In your mail, you said:
> It is a security hole, but (a) setuid shell scripts are insecure anyway
> on most systems, and (b) there's a way to avoid it:

As far as I understand, the other problem is with setuid programs calling
other programs with system(), like:
system("/bin/date");
to output date. If the IFS contains '/', someone might have a program named
bin in their path, and then...

-- 
hniksic@srce.hr              |  Student of electrical engineering
hniksic@fly.cc.fer.hr        |  University of Zagreb, Croatia
------------------------------------------------------------------
`VI' - An editor used by those heretics that don't subscribe to
       the Emacs religion.



  reply	other threads:[~1996-05-20 23:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-05-18 11:51 Zefram
1996-05-19 22:34 ` Zoltan Hidvegi
1996-05-20 15:58   ` Zefram
1996-05-20 17:21     ` Zoltan Hidvegi
1996-05-20 17:03       ` Bart Schaefer
1996-05-20 18:36         ` Zoltan Hidvegi
1996-05-20 21:09           ` Zefram
1996-05-20 22:43             ` Hrvoje Niksic [this message]
1996-05-20 22:55               ` Zefram
1996-05-20 23:08                 ` Hrvoje Niksic
1996-05-20 23:36                   ` Zefram
1996-05-20 17:54       ` Zefram
1996-05-20 22:25         ` Hrvoje Niksic
1996-05-20  1:01 ` Zoltan Hidvegi

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=199605202243.AAA17633@jagor.srce.hr \
    --to=hrvoje.niksic@public.srce.hr \
    --cc=A.Main@dcs.warwick.ac.uk \
    --cc=hniksic@public.srce.hr \
    --cc=hzoli@cs.elte.hu \
    --cc=schaefer@nbn.com \
    --cc=zsh-workers@math.gatech.edu \
    /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).