wes@ukecc.UUCP (Wes Morgan) (10/29/86)
A simple solution:
1) Assumption: Users are *going* to look around; the "cd" command
ensures that. Therefore, a default umask can take care of this
aspect of this problem.
2) One of the best methods of learning any language or operating
system is to have sample sources readily available. Why not
have a directory /usr/local/examples, containing elementary
C programs ("Hello, world\n" and the like), simple shell
procedures, et cetera. Between this directory and the man
pages, any new user should be satisfied. I know *I* would
be.
3) In order to deal with persistent snoopers, numerous solutions
are possible. Security procedures (UID checks) are easily
implemented, especially by someone who writes a program about
which he is so paranoid. Someone capable of writing, for example,
a process scheduler, has no right to gripe about unauthorized
access. Another solution is to simply have a system default
for directories such that noone else may peek. This is a restate-
ment of the "learn to unprotect rather than protect" solution.
4) Gee, folks, how about ENCRYPTION?????????? Your typical snooper
certainly doesn't have the know-how to break most encryption
schemes. Granted, it takes a little additional time, but isn't
that protection worth it?
Flames to this account, please; I'm tired of seeing "Your opinions stink!"
covering 10-30 postings.
I don't mind people peeking at *my* files; all the important stuff is
suitably protected, using combinations of the above techniques.
ACK PFHFHFHFT!!!!!
--
Wes Morgan UUCP: !cbosgd!ukma!ukecc!wes
BITNET: CS0270A9@UKCC
CSNET: wes@ecc.engr.uky.csnet
ARPANET: wes%ecc.engr.uky.csnet@csnet-relay.ARPA
" Disclaimer? Huh? You mean this was supposed to be *MY* opinion?"