Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uwm.edu!psuvax1!hsdndev!cmcl2!kramden.acf.nyu.edu!brnstnd
From: brnstnd@kramden.acf.nyu.edu (Dan Bernstein)
Newsgroups: comp.unix.wizards
Subject: Re: BSD tty security, part 3: How to Fix It
Message-ID: <28067:May315:44:3891@kramden.acf.nyu.edu>
Date: 3 May 91 15:44:38 GMT
References: <15896:Apr2714:35:3991@kramden.acf.nyu.edu> <*WC_6A$@warwick.ac.uk> <128049@tyrell.stgt.sub.org>
Organization: IR
Lines: 13

In article <128049@tyrell.stgt.sub.org> rodney@tyrell.stgt.sub.org (Rodney Volz) writes:
> Sorry for interfering, but I really don't see the point in discussing
> "write". Write does not have any S-Bit,

It does under the tty group model in BSD 4.3. More precisely: write and
talk become setgid tty (typically group 4, btw), write either doesn't
allow shell escapes (this is easiest) or resets gids properly on shell
escapes, all ttys are set to group tty, and mesg uses only the
group-write bit. This is a required step in my plan, though it's a no-op
on most BSD systems out there. It would also not be necessary under a
sane talk/write model.

---Dan