aboutsummaryrefslogtreecommitdiff
path: root/blocking-bugs
diff options
context:
space:
mode:
authorSam Hartman <hartmans@mit.edu>2006-01-29 21:14:03 +0000
committerSam Hartman <hartmans@mit.edu>2006-01-29 21:14:03 +0000
commita177821837fb86d88e43e22b57767fd5ef2515fb (patch)
tree03ee11094af5f272f85dc3f8d76ad611f44c0df7 /blocking-bugs
parenta46812b69fb353574c958396b26bce817d88e20f (diff)
downloadkrb5-a177821837fb86d88e43e22b57767fd5ef2515fb.zip
krb5-a177821837fb86d88e43e22b57767fd5ef2515fb.tar.gz
krb5-a177821837fb86d88e43e22b57767fd5ef2515fb.tar.bz2
* Fix prototype of db2 library initializer to work with changes introduced in error handling patch.hartmans/ldap-integ
* Remove thread safety flag from the LDAP plugin vftable * Work around LDAP_X_ERROR not being in all version of OpenLDAP * Work around older OpenLDAP using ldap_opt_error_number not ldap_opt_result_code * Source is in SRCTOP not BUILDTOP; kadmin/server got this wrong. * Document more blocking bugs git-svn-id: svn://anonsvn.mit.edu/krb5/users/hartmans/ldap-integ@17633 dc483132-0cff-0310-8789-dd5450dbe970
Diffstat (limited to 'blocking-bugs')
-rw-r--r--blocking-bugs6
1 files changed, 5 insertions, 1 deletions
diff --git a/blocking-bugs b/blocking-bugs
index 8b772cb..60baef7 100644
--- a/blocking-bugs
+++ b/blocking-bugs
@@ -13,7 +13,7 @@ specific data is OK.
* --with-ldap needs to be carefully considered; is OPENLDAP upper case really correct? Consider GCS and other options we already use.
-* kdc, kadmin/ldap_util, lib/kadm5/clnt/ wants err_handle.h from lib/kdb. This seems
+* kdc, kadmin/server kadmin/ldap_util, lib/kadm5/clnt/ wants err_handle.h from lib/kdb. This seems
wrong and should probably be fixed either by installing that header in
buildtop/include or something.
@@ -26,3 +26,7 @@ doesn't mess things up too much.
* I've told the kadmin client to link against -lkdb5 as a hack.
That's clearly wrong but is because of brokenness in kadm5/clnt.
+
+* The ldap plugin also serves as a library for its administrative
+interface. Determine if this is OK; I expect it to create load
+problems as the plugin directory should not be on the search path.