Xref: utzoo comp.unix.wizards:25204 alt.security:2342
Newsgroups: comp.unix.wizards,alt.security
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!psuvax1!news
From: flee@cs.psu.edu (Felix Lee)
Subject: Re: BSD tty security, part 3: How to Fix It
Message-ID: <7kdGsj9?1@cs.psu.edu>
Sender: news@cs.psu.edu (Usenet)
Nntp-Posting-Host: dictionopolis.cs.psu.edu
Organization: /home/staff/flee/.organization
References: <7299:Apr2510:22:2091@kramden.acf.nyu.edu> <12535@dog.ee.lbl.gov>
	<15896:Apr2714:35:3991@kramden.acf.nyu.edu>
Date: Mon, 29 Apr 91 02:45:46 GMT
Lines: 12

> 3. Do people think it's a problem that ``write'' can flood a terminal
> with output before the recipient has a chance to react? My version
> limits output to 500 characters per line and one line a second.

It's a form of noise ordinance.  Perhaps there are better noise
ordinances, but that one seems reasonable to me.

Of course, write-like programs shouldn't use tty devices for
rendezvous.  They should rendezvous at a service or port advertised by
the user.  I believe Zephyr does something like this.
--
Felix Lee	flee@cs.psu.edu