]> git.ipfire.org Git - thirdparty/krb5.git/commit
Don't cache referral and alternate TGT replies 649/head
authorGreg Hudson <ghudson@mit.edu>
Tue, 25 Apr 2017 21:05:23 +0000 (17:05 -0400)
committerGreg Hudson <ghudson@mit.edu>
Wed, 26 Apr 2017 17:13:16 +0000 (13:13 -0400)
commit1dc619624421002b1e64d3b8c7e270508381b3e6
tree05f890802724e517cceccfb16e3dbac2fd28560d
parente5a78d4c90d9d6968c94b0c07f2cd3835f02aa5d
Don't cache referral and alternate TGT replies

During a TGS request, if we get a TGT response that we didn't directly
ask for (a referral TGT or an alternate TGT), don't cache it.  It
would have limited value in the cache as similar operations won't look
for that TGT.  If the overall TGS operation fails and is repeated, we
could wind up caching the same entry multiple times, which doesn't
work well with our current ccache implementations.

ticket: 8579
src/lib/krb5/krb/get_creds.c
src/tests/t_crossrealm.py
src/tests/t_referral.py