Xref: utzoo comp.unix.wizards:25471 alt.security:2491 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!sdd.hp.com!wuarchive!uunet!kithrup!sef From: sef@kithrup.COM (Sean Eric Fagan) Newsgroups: comp.unix.wizards,alt.security Subject: Re: BSD tty security, part 3: How to Fix It Message-ID: <1991May08.175318.12129@kithrup.COM> Date: 8 May 91 17:53:18 GMT References: <15896: Apr2714: 35:3991@kramden.acf.nyu.edu> <1991May8.050005.26963@cbnewsh.att.com> Organization: Kithrup Enterprises, Ltd. Lines: 17 In article <1991May8.050005.26963@cbnewsh.att.com> wcs@cbnewsh.att.com (Bill Stewart 908-949-0705 erebus.att.com!wcs) writes: >* "write" is for rudely interrupting people who haven't pre-arranged > some kind of talk program. The standard write programs let > you prevent people (other than root) from interrupting you > if you want. It also works as a crude "talk". talk doesn't work too well a) when talking from a non-sun to a sun, b) when network bandwidth is on the order of 30 bytes a second, and c) when you don't have a terminal capable of running a full-screen program. While write works for all three cases (for (b) I use 'mode l' from telnet, it helps a lot), you need to have an account on the target machine. -- Sean Eric Fagan | "I made the universe, but please don't blame me for it; sef@kithrup.COM | I had a bellyache at the time." -----------------+ -- The Turtle (Stephen King, _It_) Any opinions expressed are my own, and generally unpopular with others.