Skip Menu |

Subject: git commit

Fix KDC lock persistence on error conditions

If k5db2_dbopen() returns an error, krb5_db2_lock() can return an
error without unlocking the lock file. This lock will persist until
krb5_db2_lock() executes successfully, preventing kadmind from making
changes to the KDB. One possible trigger is running out of file
Author: Tom Yu <>
Commit: 047afa2244c33ef54805ebf0436db42c12e83332
Branch: krb5-1.9
src/plugins/kdb/db2/kdb_db2.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)