Xref: utzoo comp.unix.wizards:25711 alt.security:2600
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!hsdndev!cmcl2!kramden.acf.nyu.edu!brnstnd
From: brnstnd@kramden.acf.nyu.edu (Dan Bernstein)
Newsgroups: comp.unix.wizards,alt.security
Subject: Re: BSD tty security, part 3: How to Fix It
Message-ID: <19515:May2122:03:3191@kramden.acf.nyu.edu>
Date: 21 May 91 22:03:31 GMT
References: <19313@rpp386.cactus.org> <3690:May1921:22:5191@kramden.acf.nyu.edu> <19317@rpp386.cactus.org>
Organization: IR
Lines: 14

In article <19317@rpp386.cactus.org> jfh@rpp386.cactus.org (John F Haugh II) writes:
> What
> happens to a trojan horse that gains access to the =PTY= =AFTER=
> the user logs in?

If that can happen, then you're not talking about a Trojan Horse; you're
talking about a complete failure in security. If a program can do that,
it can redirect all further input from and output to the terminal, and
the user is up the creek. Why do you care what happens past that?

What I'm doing is making sure that such programs won't get access to the
pseudo-tty in the first place. *That's* security.

---Dan