[11174] in Kerberos-V5-bugs
[krbdev.mit.edu #6506] SVN Commit
daemon@ATHENA.MIT.EDU (Tom Yu via RT)
Mon Sep 28 16:28:06 2009
Mail-Followup-To: rt@krbdev.mit.edu
mail-copies-to: never
From: "Tom Yu via RT" <rt-comment@krbdev.MIT.EDU>
In-Reply-To: <rt-6506@krbdev.mit.edu>
Message-ID: <rt-6506-31744.0.605677674359626@krbdev.mit.edu>
To: "'AdminCc of krbdev.mit.edu Ticket #6506'":;"'AdminCc of krbdev.mit.edu Ticket #6506'":;@MIT.EDU
Date: Mon, 28 Sep 2009 20:27:11 +0000 (UTC)
Reply-To: rt-comment@krbdev.MIT.EDU
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krb5-bugs-bounces@mit.edu
pull up r22397 from trunk
------------------------------------------------------------------------
r22397 | ghudson | 2009-06-01 18:39:31 -0400 (Mon, 01 Jun 2009) | 17 lines
ticket: 6506
subject: Make results of krb5_db_def_fetch_mkey more predictable
tags: pullup
target_version: 1.7
krb5_db_def_fetch_mkey tries the stash file as a keytab, then falls
back to the old stash file format. If the stash file was in keytab
format, but didn't contain the desired master key, we would try to
read a keytab file as a stash file. This could succeed or fail
depending on byte order and other unpredictable factors. The upshot
was that one of the libkadm5 unit tests (init 108) was getting a
different error code on different platforms.
To fix this, only try the stash file format if we get
KRB5_KEYTAB_BADVNO trying the keytab format. This requires reworking
the error handling logic.
http://src.mit.edu/fisheye/changelog/krb5/?cs=22795
Commit By: tlyu
Revision: 22795
Changed Files:
U branches/krb5-1-7/src/lib/kdb/kdb_default.c
_______________________________________________
krb5-bugs mailing list
krb5-bugs@mit.edu
https://mailman.mit.edu/mailman/listinfo/krb5-bugs
