Skip Menu |
 

Date: Wed, 3 Oct 2012 17:20:01 -0500
Subject: krb5_db_delete_principal() can fail to unlock ulog
From: Nico Williams <nico@cryptonector.com>
To: krb5-bugs@mit.edu
Well, not really, because there are no KDB backends that lack a delete
method... but if there were any such, then krb5_db_delete_principal()
would fail to unlock the ulog. This is a *very* minor bug.
From: ghudson@mit.edu
Subject: SVN Commit

krb5_db_delete_principal() can fail to unlock ulog

Not really: only when the KDB backend lacks a delete method. Still.

https://github.com/krb5/krb5/commit/e41971145349e1f55b6cb3336c014bd8edcb22da
Author: Nicolas Williams <nico@cryptonector.com>
Committer: Greg Hudson <ghudson@mit.edu>
Commit: e41971145349e1f55b6cb3336c014bd8edcb22da
Branch: master
src/lib/kdb/kdb5.c | 4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)