HP3000-L Archives

July 2000, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Stigers, Greg [And]" <[log in to unmask]>
Reply To:
Stigers, Greg [And]
Date:
Tue, 11 Jul 2000 12:50:23 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines)
X-no-Archive:yes
IIRC, some version of a Windows ResKit had a Password List "Editor"  that
allowed you to blow away entries, presumably because of this problem. It did
not allow you to edit or even see the password saved except in its encrypted
form.

Greg Stigers
http://www.cgiusa.com

-----Original Message-----
From: Michael L Gueterman [mailto:[log in to unmask]]
Sent: Tuesday, July 11, 2000 11:28 AM
To: [log in to unmask]
Subject: Re: Samba Password Behavior

> The other insidious thing in I noticed in WinDoze is
> when you're prompted for a password there's that
> little check box to save it, (it goes into your
> .pwl file.)  So if you change your password on the
> host, the user has to delete his .pwl file and
> build a new one.  (Or make sure he never has the
> box checked, if he misses unchecking it once ....
> same story.)
>

In some earlier incarnations of the Windows password caching mechanism,
if the cached password was invalid you were out of luck and had to
purge the file and start from scratch.  I believe that for a while now,
if the cached password was invalid, windows would toss up the password
dialog box and allow you to enter the new one.  It's been a while since
I looked into this though, so....

ATOM RSS1 RSS2