[37280] in Kerberos

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

Re: end of key table reached error

daemon@ATHENA.MIT.EDU (Benjamin Kaduk)
Fri Oct 30 21:50:19 2015

Date: Fri, 30 Oct 2015 21:49:57 -0400 (EDT)
From: Benjamin Kaduk <kaduk@mit.edu>
To: vishal <vicky.recw@gmail.com>
In-Reply-To: <5633D1D4.5080104@openfortress.nl>
Message-ID: <alpine.GSO.1.10.1510302148400.26829@multics.mit.edu>
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, 30 Oct 2015, Rick van Rein wrote:

> Hi Vishal,
>
> > I think there is some issue with keytab file , I see multiple kvno in
> > keytab i.e 74 & 75. Is it practical?We have 1.7 release.
>
> This is not uncommon; these are key version numbers.  They help to distinguish various keys assigned to a particular principal.  RFC 4120 says

Rick skipped the important part, namely that the krb5 1.7 release is
ancient and has been out of support for years.  (I still don't think we
know of a specific bug even in that old release that would cause this
behavior, but trying a current version is probably worthwhile.)

-Ben
________________________________________________
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