[35746] in Kerberos

home help back first fref pref prev next nref lref last post

Clock skew too great status code

daemon@ATHENA.MIT.EDU (Arpit Srivastava)
Wed Feb 5 03:37:05 2014

MIME-Version: 1.0
Date: Wed, 5 Feb 2014 14:06:35 +0530
Message-ID: <CAEvOXU5OxC+pm9hJcbD=h5nfZmECZs+Ddfp_xPawwQtMrYScRw@mail.gmail.com>
From: Arpit Srivastava <arpit.orb@gmail.com>
To: kerberos <kerberos@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu

Hi,

What is the difference between these two minor status codes ?

 -1765328373 KRB5KDC_ERR_NEVER_VALID Requested effective lifetime is
negative or too short
and
 -1765328347 KRB5KRB_AP_ERR_SKEW Clock skew too great

Because both of them seem to be getting generated when time on the
client-side is incorrect.

I also obseved that, in case of clock skew is great - I am getting
credentials expired error code instead of clock skew too great error code.
Is there any explaination for this behaviour.

Please help !

Arpit
________________________________________________
Kerberos mailing list           Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos

home help back first fref pref prev next nref lref last post