Date: Tue, 2 May 1995 12:49:43 +0000 (GMT) From: sos@FreeBSD.org (Soren Schmidt) To: peter@bonkers.taronga.com (Peter da Silva) Cc: ache@astral.msk.su, julian@ref.tfs.com, terry@cs.weber.edu, hackers@FreeBSD.org, pritc003@maroon.tc.umn.edu, sos@login.dknet.dk Subject: Re: Screen print capability Message-ID: <199505021122.AA27217@dkuug.dk> In-Reply-To: <199505020926.EAA01671@bonkers.taronga.com> from "Peter da Silva" at May 2, 95 04:26:39 am
next in thread | previous in thread | raw e-mail | index | archive | help
In reply to Peter da Silva who wrote: > > > It is well known backdoor and it is MUA itself problem (MUA need > > to be fixed). > > All other stuff (wall,write,talk) already care about it using isprint(). > > Every program anyone might write? That includes the example I gave, with > "cat"? How about "telnet"? No, the escape sequence interface for this is > terribly IBM mainframe anyway... an ioctl or (even better) a separate /dev > file that you can read the screen from is much much cleaner. Erm, I guess its my turn to put in some $0.02's What I have in mind to do (actually on my LONG todolist), is implementing a device entry /dev/screen or whatever, which will give you the current screen image with attributes size the works... I have deliberately not implemented SCO's esc. seq. for all the stated reasons... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org | sos@kmd-ac.dk) FreeBSD Core Team ..
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505021122.AA27217>