Aazure.616
net.followup
utcsrgv!utzoo!decvax!ucbvax!ihnss!cbosg!teklabs!tekmdp!azure!stevenm
Tue Mar 9 22:04:10 1982
Re: Terminal Security Problem
Arghh! Terminal Paranoia!
"No reasonable reason why a terminal should have a block send command
which the host can send?"
Horse Puckey!! I have an Ann Arbor Ambassador, and a nifty little program
which I call 'sss' which takes a snapshot of the memory (screen)
into a file. This is extremely useful for capturing stuff that comes
out to the screen (e.g. diagnostics) which exist nowhere else. I use
it every day.
I can think of a dozen other uses for block-send mode.
What this whole issue boils down to is this: if you work in a 'hostile'
environment, then you might as well work on ASR-33's, because if you
don't, and you are truely worried about security, you will otherwise
have to so hamstring you software that you'd never get any work done.
If you DON'T work in a hostile environment, as I suspect is true of
most people running UNIX, then why worry about it? You catch the young
squirt hacker that does it, shake him/her by the hair, an tell him/her
that the next time they do such a thing you will break their typing
finger.
Oh, and make sure you don't tell the press.
S. McGeady
-----------------------------------------------------------------
gopher://quux.org/ conversion by John Goerzen <
[email protected]>
of
http://communication.ucsd.edu/A-News/
This Usenet Oldnews Archive
article may be copied and distributed freely, provided:
1. There is no money collected for the text(s) of the articles.
2. The following notice remains appended to each copy:
The Usenet Oldnews Archive: Compilation Copyright (C) 1981, 1996
Bruce Jones, Henry Spencer, David Wiseman.
