[2797] in WWW Security List Archive
Re: A problem with Navigator's cache -Reply
daemon@ATHENA.MIT.EDU (Adam Shostack)
Sun Aug 25 20:47:34 1996
From: Adam Shostack <adam@homeport.org>
To: jsw@netscape.com
Date: Sun, 25 Aug 1996 19:34:24 -0500 (EST)
Cc: adam@homeport.org, www-security@ns2.rutgers.edu
In-Reply-To: <3220CA32.13D@netscape.com> from "Jeff Weinstein" at Aug 25, 96 02:48:34 pm
Errors-To: owner-www-security@ns2.rutgers.edu
Jeff Weinstein wrote:
| Adam Shostack wrote:
| > So the executable gets its own path name, and then locks for
| > $Netscapedir/netscape.lck?
| >
| > cp /usr/local/bin/netscape /tmp
| > /tmp/netscape
| >
| > sigh. If the program runs under the user's control, then the path to
| > the netscape.lck must be hardcoded and fully qualified, such as
| > /usr/local/lib/netscape/netscape.lck
|
| In a properly configured environment this will not work. Your
| firewall, proxy and corporate servers can be configured to only
| accept connections from a navigator with the correct lock file.
I'm glad to hear it, but, is this documented? Can I do this
without buying Netscape's proxy?
Adam
--
"It is seldom that liberty of any kind is lost all at once."
-Hume
