Skip Menu |
 

Date: Wed, 18 Feb 2004 14:49:56 -0500
From: "Chris Hallenbeck" <cthallen@aol.net>
Subject: kfw2.6b6: problem w/ expired passwords
To: kfw-bugs@MIT.EDU
I intentionally set my password to expire using:

modprinc +needchange cthallen
and then later tested using
modprinc -pwexpire now cthallen

When using KfW2.6b6 through either leash32 or the
command line kinit, I am told:
"kinit(v5): Password has expired while getting initial credentials"
but I am never afforded an opportunity to change my
password -- unlike the UNIX kinit which prompts me to
change my password.

Were this the only issue, it would only be a minor
annoyance *grin*, but the problem is worse. When I
use leash32 and select "Change Password", I enter my
old password & my new one twice. At this point I
receive a dialog:
"
Ticket initialization failed.

Kerberos 5: Password has expired (error 23)
"

My response is "yes, I know my password has expired.
That's why I want to change it!" ;-)


Am I encountering a design feature or a bug on the
part of KfW2.6b6?


Thanks!

-Chris
Download smime.p7s
application/x-pkcs7-signature 3.5KiB

Message body not shown because it is not plain text.

As an additional note, I've got an old "Kerberos V5 for Windows 32-bit:
Version 1.12" that has the expected behavior when attempting to change
an already expired password.
Subject: kfw2.6: problem w/ expired passwords
[guest - Wed Feb 18 15:36:16 2004]:

Show quoted text
> As an additional note, I've got an old "Kerberos V5 for Windows 32-bit:
> Version 1.12" that has the expected behavior when attempting to change
> an already expired password.

I am going to look at this problem and try to slip a fix into KFW 2.6.1
if I can. Did the old Kerberos 5 for Windows have "leash32.exe" as the
ticket manager? Or was it another tool?
I found the problem. this will be fixed in KFW 2.6.1 Beta 2 which
should be announced tonight or tomorrow.