[33756] in Kerberos
how to check tkt for expiration including clockskew?
daemon@ATHENA.MIT.EDU (Chris Hecker)
Thu Aug 11 05:52:34 2011
Message-ID: <4E43A657.80006@d6.com>
Date: Thu, 11 Aug 2011 02:52:23 -0700
From: Chris Hecker <checker@d6.com>
MIME-Version: 1.0
To: "kerberos@mit.edu" <kerberos@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
So, the clockskew is in the context, which is an opaque struct (unless
you include k5-int.h). All the times validation functions seem to be
krb5int_*. ksu and others include k5-int.h so they can make their own
check_exp function. What's a well-behaved app supposed to do to check
for ticket expiration? Should I hard code 5*60 in there because I know
I don't have a different value set?
Thanks,
Chris
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
