Skip Menu |
 

From: ghudson@mit.edu
Subject: SVN Commit

Use blocking locks in krb5kdc and libkadm5srv

We don't really need or want to use non-blocking locks, and we certainly
don't want to sleep(1) in krb5kdc (possibly several times, as there was
a loop over this) when either of the principal or policy DB is locked.
Some callers still request non-blocking locks, and ctx_lock() still
honors this.

https://github.com/krb5/krb5/commit/b858e776ece87756202d4c646931d35bd407e3ea
Author: Nicolas Williams <nico@cryptonector.com>
Committer: Greg Hudson <ghudson@mit.edu>
Commit: b858e776ece87756202d4c646931d35bd407e3ea
Branch: master
src/plugins/kdb/db2/kdb_db2.c | 52 +++++++++++++++--------------------------
src/plugins/kdb/db2/kdb_db2.h | 2 -
2 files changed, 19 insertions(+), 35 deletions(-)
From: ghudson@mit.edu
Subject: SVN Commit

Use blocking locks for policy DB

In the db2 kdb module, use blocking locks for the policy DB as well as
the principal DB.

https://github.com/krb5/krb5/commit/e03a59074017dde6e0c524efcba9476aec064d17
Author: Greg Hudson <ghudson@mit.edu>
Commit: e03a59074017dde6e0c524efcba9476aec064d17
Branch: master
src/plugins/kdb/db2/adb_openclose.c | 25 ++++++-------------------
1 files changed, 6 insertions(+), 19 deletions(-)