summaryrefslogtreecommitdiff
path: root/testsuite/build_farm/torture-LOCK4.test
diff options
context:
space:
mode:
authorGerald Carter <jerry@samba.org>2007-06-13 20:49:20 +0000
committerGerald (Jerry) Carter <jerry@samba.org>2007-10-10 12:23:19 -0500
commit4caefdf348857577343075ae647e29a0ac904ae0 (patch)
treed39cb0c6509235d6d370a097a7a55c085f07dc4b /testsuite/build_farm/torture-LOCK4.test
parentbfbf08adfffc3967a2866626d8e54fb8849a841b (diff)
downloadsamba-4caefdf348857577343075ae647e29a0ac904ae0.tar.gz
samba-4caefdf348857577343075ae647e29a0ac904ae0.tar.bz2
samba-4caefdf348857577343075ae647e29a0ac904ae0.zip
r23474: Here's a small patch that disables the libkrb5.so replay cache
when verifying a ticket from winbindd_pam.c. I've found during multiple, fast, automated SSH logins (such as from a cron script) that the replay cache in MIT's krb5 lib will occasionally fail the krb5_rd_req() as a replay attack. There seems to be a small window during which the MIT krb5 libs could reproduce identical time stamps for ctime and cusec in the authenticator since Unix systems only give back milli-seconds rather than the micro-seconds needed by the authenticator. Checked against MIT 1.5.1. Have not researched how Heimdal does it. My thinking is that if someone can spoof the KDC and TDS services we are pretty hopeless anyways. (This used to be commit cbd33da9f78373e29729325bbab1ae9040712b11)
Diffstat (limited to 'testsuite/build_farm/torture-LOCK4.test')
0 files changed, 0 insertions, 0 deletions