Fix returning KDB_NOENTRY in find_alternate_tgs()
After searching for a cross-realm TGS entry to provide to a client as a
referral, if we're all set to return a success code but aren't actually
returning an entry, we should be returning an error. We might not do so
because we don't compare the right value against NULL.
This corrects an error in a redundant check in the patch for
CVE-2013-1417. The error in the check cannot occur in practice
because the other part of the patch for CVE-2013-1417 prevents it, but
static analyzers can flag the erroneous check.
[firstname.lastname@example.org: edit commit message]
(cherry picked from commit 90cbf4eb60d8ec3c083195ba4a050a31ea36be0b)
Author: Nalin Dahyabhai <email@example.com>
Committer: Tom Yu <firstname.lastname@example.org>
src/kdc/do_tgs_req.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)