Merge remote-tracking branch 'origin/master' into OPENLDAP_REL_ENG_2_5

[openldap] / TODO

diff --git a/TODO b/TODO
index 7a798efe991c6e54c7a5f209850cefb57f1c233f..03d02d9d878dfee252aacb72894b76aa26153ab7 100644 (file)
--- a/TODO
+++ b/TODO
@@ -33,3 +33,29 @@ ITS#7926 - [18:19] <hyc> this is going to be a WONTFIX for 2.4, I think
 <hyc> I need to publish a spec for PREPARE/2-phase commit in LDAP TXNs and integrate that into lmdb and back-mdb
 
 Update slapo-unique to have an option to disable manageDSAit (ITS#8245)
+
+Leftover bits from ITS#8294 -- Drop custom SHA2 code, use default crypto library SHA2 functions instead
+  May need to document minimum crypto library version requirements
+  Can also include sha2.c in slapd-sha2.c and make everything static
+
+Matching rules for olc* attrs, see also ITS#8341
+
+New syslog engine
+
+[12:45] <hyc> I meant regcomp and regexec
+[12:45] <hyc> mainly - compile a pattern, then fill in substitution parameters later
+[12:46] <hyc> yes but the idea is still based on numbered substitution parameters
+[12:47] <hyc> it's a pretty obvious approach, and with regex, time-tested.
+[12:48] <hyc> I may try to sneak it into OpenLDAP 2.5
+
+
+Overhaul overlays and backends, see ITS 6166
+
+(In relation to a discussion about slapo-chain)
+<hyc> anyway, the nicer ting to fix would be in 2.5, push all of the repl consumer code into its own overlay
+<hyc> in that case, updateref would be processed wherever the overlay was configured
+<hyc> so no longer tied to the frontend
+<hyc> it would also make it more feasible to have multiple different consumer configs in a single DB, each with their own provider URL (and thus their own updateref)
+<hyc> I would think we can get rid of the update ref directive entirely, just point all writes to that consumer's provider.
+
+Update dynlist so it works with search filters, so that autogroup can be deleted