[32636] in Kerberos
Re: Kerberos and 2038 date rollover in effect - how to fix?
daemon@ATHENA.MIT.EDU (Greg Hudson)
Fri Sep 3 16:52:33 2010
From: Greg Hudson <ghudson@mit.edu>
To: Tucks <jez.tucker@rushes.co.uk>
In-Reply-To: <a65230e8-31a2-4b14-b65b-d3291420c6bb@y12g2000prb.googlegroups.com>
Date: Fri, 03 Sep 2010 16:52:28 -0400
Message-ID: <1283547148.5992.1162.camel@ray>
Mime-Version: 1.0
Cc: "kerberos@mit.edu" <kerberos@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
On Fri, 2010-09-03 at 13:00 -0400, Tucks wrote:
> Does anyone have any idea how to force through the new ticket expiry
> change? According to all the documentation I've read, it should be
> good, but isn't. I've probably missed something trivial.
No propagation should be necessary between the database and the KDC
process (or kadmind).
However, propagation may be necessary between master and slave KDCs, if
you have slaves.
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
