A failure count interval of 0 caused krb5_ldap_lockout_check_policy to
pass the lockout check (but didn't cause a reset of the failure count
in krb5_ldap_lockout_audit).  It should be treated as forever, as in
the DB2 back end.

This bug is the previously unknown cause of the assertion failure
fixed in CVE-2011-1528.

https://github.com/krb5/krb5/commit/4a84d4137426d0951d5565adef30efebab719d23
Commit By: ghudson
Revision: 25480
Changed Files:
U   trunk/src/kadmin/cli/kadmin.M
U   trunk/src/plugins/kdb/ldap/libkdb_ldap/lockout.c