Looking through other users' (unprotected) files

[Jeff Siegal]

>In article <810 at aimmi.UUCP> gilbert at aimmi.UUCP (Gilbert Cockton) writes:
>The first things a new user should be taught include:
>	- how to use "chmod" to make a "personal" (safe) directory and
>	- how to use "chmod" to protect an individual file.
>Not using "chmod", then screaming about someone reading your files, is like
>not locking your house and complaining when a burglar walks in.

>[Mark Levine compares Unix to a hotel]

While I'm not sure I agree with Mark, that users necessarily expect
security to be activated by default, I _definitely_ disagree with
Gilbert's implied contention that burglarizing a house with unlocked
doors is not illegal, immoral, and generally unacceptable behavior.  I
have lived in an area where people generally do _not_ lock their doors
at all times, and the police take burglaries very seriously, whether
or not the doors were locked.

Does someone's home being unlocked give you the right to violate it
without permission?  Does someone's desk being unlocked, or in an
unlocked office give you the right to look through it?  Does someone's
files being in a world-readable directory, or set world-readable give
you the right to read them.  I think not.  

If you want to read someone's files, whether you are able to read them
or not, ASK PERMISSION.  If they want to share, fine.  If they do not
give you permission, don't read them, whether you are able to or not.

Why is it that people often become so confused about such basic issues
as privacy and individual rights as soon as the word "computer" enters
the conversation?

Jeff Siegal