[1293] in WWW Security List Archive

home help back first fref pref prev next nref lref last post

Re: caching protected documents

daemon@ATHENA.MIT.EDU (David W. Morris)
Wed Dec 20 23:55:19 1995

Date: Wed, 20 Dec 1995 18:29:55 -0800 (PST)
From: "David W. Morris" <dwm@shell.portal.com>
To: Brain21 <brain21@montag33.residence.gatech.edu>
cc: www-security@ns1.rutgers.edu
In-Reply-To: <Pine.LNX.3.91.951220163457.20447N-100000@montag33.residence.gatech.edu>
Errors-To: owner-www-security@ns2.rutgers.edu



On Wed, 20 Dec 1995, Brain21 wrote:

> What does this mean??  This is NOT necessarily a cacheing problem!!!

What this means is that your organization should have a policy about
unattended logged in terminals.  If you care, logoff, lock your 
display, lock the office, etc. When you provide the UID/pw it is 
similar to login to any kind of protected service, a mainframe, a local
unix system, a NETWARE server, etc.

In the end you must practice safe computing if you care what your 
computed results are...


Dave Morris

home help back first fref pref prev next nref lref last post