summaryrefslogtreecommitdiffstats
path: root/src/plugins/locate/python/python.exports
diff options
context:
space:
mode:
authorGreg Hudson <ghudson@mit.edu>2012-01-11 21:20:08 +0000
committerGreg Hudson <ghudson@mit.edu>2012-01-11 21:20:08 +0000
commit37b0e55e21926c7875b7176e24e13005920915a6 (patch)
tree841661409c27c201ba7e7ef626955fd670cef4cc /src/plugins/locate/python/python.exports
parent551d3788241b34adb162efd63f6e7ace6afdcca1 (diff)
downloadkrb5-37b0e55e21926c7875b7176e24e13005920915a6.tar.gz
krb5-37b0e55e21926c7875b7176e24e13005920915a6.tar.xz
krb5-37b0e55e21926c7875b7176e24e13005920915a6.zip
Fix spurious clock skew caused by gak_fct delay
In get_in_tkt.c, a time offset is computed between the KDC's auth_time and the current system time after the reply is decrypted. Time may have elapsed between these events because of a gak_fct invocation which blocks on user input. The resulting spurious time offset can cause subsequent TGS-REQs to fail and can also cause the end time of the next AS request to be in the past (issue #889) in cases where the old ccache is opened to find the default principal. Use the system time, without offset, for the request time of an AS request, for more predictable kinit behavior. Use this request time, rather than the current time, when computing the clock skew after the reply is decrypted. ticket: 7063 git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@25644 dc483132-0cff-0310-8789-dd5450dbe970
Diffstat (limited to 'src/plugins/locate/python/python.exports')
0 files changed, 0 insertions, 0 deletions