Ticket History #6506: Make results of krb5_db_def_fetch

# Mon Jun 01 18:39:33 2009 ghudson@mit.edu (Greg Hudson) - Ticket created

From:	ghudson@mit.edu
Subject:	SVN Commit

Download (untitled) / with headers
text/plain 763B

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.

https://github.com/krb5/krb5/commit/9d4a7b700805858bc1a091cd6561ee9f5aef20af
Commit By: ghudson
Revision: 22397
Changed Files:
U trunk/src/lib/kdb/kdb_default.c

# Mon Jun 01 18:39:34 2009 ghudson@mit.edu (Greg Hudson) - Requestor ghudson@mit.edu (Greg Hudson) added

# Mon Jun 01 18:39:34 2009 ghudson@mit.edu (Greg Hudson) - Status changed from 'new' to 'review'

# Mon Jun 01 18:39:34 2009 ghudson@mit.edu (Greg Hudson) - Tags pullup added

# Mon Jun 01 18:39:34 2009 ghudson@mit.edu (Greg Hudson) - Target_Version 1.7 added

# Mon Jun 01 19:03:12 2009 tlyu (Taylor Yu) - Version_reported 1.7 added

# Thu Jul 02 20:43:52 2009 tlyu (Taylor Yu) - Component krb5-kdc added

# Thu Jul 02 20:43:52 2009 tlyu (Taylor Yu) - Target_Version 1.7 changed to 1.7.1

# Mon Sep 28 16:27:11 2009 tlyu (Taylor Yu) - Status changed from 'review' to 'resolved'

# Mon Sep 28 16:27:11 2009 tlyu (Taylor Yu) - Correspondence added

From:	tlyu@mit.edu
Subject:	SVN Commit

Download (untitled) / with headers
text/plain 1KiB

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.

https://github.com/krb5/krb5/commit/4582a1b450f58116745587911370b7035fc41b50
Commit By: tlyu
Revision: 22795
Changed Files:
U branches/krb5-1-7/src/lib/kdb/kdb_default.c

# Mon Sep 28 16:27:45 2009 tlyu (Taylor Yu) - Version_Fixed 1.7.1 added

# Wed Dec 16 18:02:54 2015 tlyu (Taylor Yu) - CustomField pullup deleted

Ticket History #6506: Make results of krb5_db_def_fetch_mkey more predictable