You either have to wait for the cookie to expire or find out which user
the cookie is for and have the LISTSERV maintainer at the site in question
do a PWC DELETE to get rid of the user's password.  Then the next time someone
tries to log in, the cookie doesn't work and you get the login screen.

Quite frankly, IMHO this is a major browser problem (the inability to easily
edit/delete existing cookies) and the only thing that makes it a LISTSERV
problem is that people are setting cookies when they shouldn't be.  Francoise
is right, users in clusters or otherwise shared computers simply shouldn't
set cookies.

Note that getting rid of cookies.txt <should> work but that at least in
my case, there are two copies of cookies.txt (NS 3.01 Gold), one in the
"Netscape" directory and one in the "Program" directory underneath it.
It's the one in the "Program" directory that my copy of NetScape actually
uses.  (The other one must be from an older version, I guess)  Anyway,
I tried editing cookies.txt a week or so ago to get rid of the trash
cookies and that ended up hosing <all> of my cookies, not just the ones
I deleted :)  So I guess I ended up with a file of broken cookies, eh? :)

Hmm, on NS 4.x you likely have multiple cookies.txt files based on the
current logon...so are you sure you have the right copy of the file?

Nathan

On Mon, 30 Mar 1998 09:22:47 +0000 Angus said:
>> People using a shared computer should NEVER ask to set a cookie for
>> viewing lists. It completely defeats the security.
>
>Well the problem it is is.. it's done and may have been done some
>time ago.  I know I apparently have a magic cookie set on my computer
>with one address and it won't allow me to access archives of lists
>I'm on under a different address.. and I can't see anyway to change
>that for me.. or for the people using the shared computers.
>
>> The cookies BTW are not set for a particular list, but for the whole
>> server.
>
>That's a big part of the problem. Subscribers are now locked out of
>lists on servers because susbscribers to others lists on that server
>set passwords :((
>
>The question is still.. is there anyway to get around this?
>
> ........Cleo  [log in to unmask]