From: Christopher Hull <nozefngr@apple.com>
To: <jsw@netscape.com>
Message Hash: 0ae7a4788ebcd8c8643bb7280a6e7f1a5b330722beed97fe56a34037cccecc6e
Message ID: <199607160116.SAA24413@apple.com>
Reply To: N/A
UTC Datetime: 1996-07-16 12:44:36 UTC
Raw Date: Tue, 16 Jul 1996 20:44:36 +0800
From: Christopher Hull <nozefngr@apple.com>
Date: Tue, 16 Jul 1996 20:44:36 +0800
To: <jsw@netscape.com>
Subject: Re: CookieScan 0.0 rev 0
Message-ID: <199607160116.SAA24413@apple.com>
MIME-Version: 1.0
Content-Type: text/plain
>Subject: Re: CookieScan 0.0 rev 0
>Sent: 7/15/96 4:57 PM
>Received: 7/15/96 6:01 PM
>From: Jeff Weinstein, jsw@netscape.com
>To: Christopher Hull, nozefngr@apple.com
>CC: cypherpunks@toad.com
>
>Christopher Hull wrote:
>> What I imagine is a little utility that would
>> display the cookies stashed on a machine and
>> give the user the option to either delete or
>> <snicker> edit </snicker> any given cookie.
>> (Hey, it¹s *your* computer, not the website¹s).
>
> I doubt that you will have much luck here. Many (most??) sites
>that use cookies tend to encode or obscure them so that they are not
>human readable. Certainly anyone doing something questionable
>will obscure their cookies so that they will not be user readable
>or editable.
>
I agree. Editing is problematic.
It would be difficult to decode intentionally
hidden information. The user may suspect strange and not
obvious stuff in a site's given cookie. Then what may
happen is the user will "vote with their mouse" and stop
using a site that encripts cookie data (or perhaps not).
In any case the user will at least have the knowledge
that the cookie exists. Those that do not encrypt may
provide other interesting information.
-Chris
...
... smtp: nozefngr@apple.com
.. page: 1.800.680.7351
.. http: http://virtual.net/Personal/nozefngr/
.. icbm: lat37*21'.lon121*5'
..
.. the kabuki project: http://remarque.berkeley.edu/kabuki/
Return to July 1996
Return to “Rabid Wombat <wombat@mcfeely.bsfs.org>”