[8031] in Kerberos
Re: workaround for default max_life of 0
daemon@ATHENA.MIT.EDU (Christoph Hoegl)
Wed Sep 18 20:13:59 1996
To: fleminpm@som.siu.edu
In-Reply-To: fleminpm's message of Wed, 18 Sep 1996 15:33:06 -0500.
<32405C82.73E7@som.siu.edu>
Cc: kerberos@MIT.EDU
Date: Thu, 19 Sep 1996 01:54:48 +0200
From: Christoph Hoegl <darkwing@bsdd.regensburg.com>
> > =
> > The workaround to the problem is to add a max_life field to kdc.conf,=
> > like this:
> > =
> > [realms]
> > DEMO.COM =3D {
> > <other stuff>
> > max_life =3D 10h 0m 0s
> > <other stuff>
> > }
> > =
> > The correct fix is for KADM5 to assume a reasonable default if
> > max_life is not specified, such as 8 hours. This will be fixed in th=
e
> > next release.
> > =
> > Barry
> > =
> =
> I set the max_life exactly like above but still no luck. I can manually=
> change the max life of a principal but if I create a new one it gets a
> default life of 0h 0m 0s. I even recreated the principal database but
> still no luck.
> =
> Paul Fleming
Maybe I=B4m wrong but i think it might be worth trying:
1. is your kdc.conf pointing back to your krb5.conf?
(I made it pointing somewhere else and got the same result)
2. max_renewable_life is set correctly?
3. have you checked all files that get installed?
(using an older kinit may lead to some confusing errors
(I myself got klists which showed dates in other centuries:-) ))
Hope it helps,
Christoph
-- =
Christoph Hoegl / darkwing@bsdd.regensburg.com / (Darkwing@berkeley.edu)
Siedlungsstr. 18 93128 Regenstauf Germany Fax:+49 940270611
Tellerrd. 12a 93720 Berkeley CA USA Fax:+1 (510) 642 1043
