openldap-devel

openldap-devel@openldap.org

1418 discussions

ITS#8286 continued
by Quanah Gibson-Mount 18 Jun '19

18 Jun '19

I found a few stray items that still need matching rules. All were trivially straight forward except one for slapo-chain: { "chain-chaining", "args", 2, 4, 0, ARG_MAGIC|ARG_BERVAL|CH_CHAINING, chain_cf_gen, "( OLcfgOvAt:3.1 NAME 'olcChainingBehavior' " "DESC 'Chaining behavior control parameters (draft-sermersheim-ldap-chaining)' " "SYNTAX OMsDirectoryString SINGLE-VALUE )", NULL, NULL }, At the moment, based on the man page description, I was thinking: "EQUALITY caseExactMatch " for the matching rule. Anyone have an opinion for caseIgnoreMatch being better? Thanks, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

2 2

ITS review 6/4/2019
by Quanah Gibson-Mount 13 Jun '19

13 Jun '19

All of the following have patches and need review/approval. Any with **** I consider desired for the next releases of LMDB & OpenLDAP: LMDB related ITSes ---------------------- **** ITS#8986 - Fix LMDB for FreeBSD12 (has patch, IPR OK) ITS#8739 - liblmdb - Fixes fsync check on FreeBSD (has patch, IPR not needed) OpenLDAP related ITSes for RE24 ------------------------------- ITS#7042 - slapd/syncrepl - Allow disconfiguring TLS settings (has patch, IPR OK) ITS#7721 - contrib/lastbind - allow authtimestamp forwarding with updateref (44e9bda0e42f40e0baf0a2c0ef733eb757abd366) ITS#7770 - back-monitor - Add mdb_stat info (e19c683c41e14365d28e82278eec1d8b12c71d4c , 6e2bac6465bb81a8c1aeb083b6dc497eb4187264 ) **** ITS#7996, ITS#8450 - libldap - Fix race condition (has patch, IPR OK) **** ITS#8037 - slapd - Fix delta-syncrepl with relax (cb9a4d01bc1ecf1eeb3fb7ef39067b2b30b6c545) **** ITS#8167 - libldap - fix non-blocking TLS (46c93e41f43da7f16270179c6eff75e450617329) ITS#8349 - Fix ppolicy behavior with pwdHistory **** ITS#8427 - slapd/syncrepl - Fix broken behavor for TLS options (has patch, IPR OK) ITS#8508 - liblunicode - Fix ucgendat (cc99da182f53d3d4f3874703643b277773717af3) **** ITS#8637 - slapd-ldap - Correctly reject invalid config with slapd-config (has patch, IPR OK) **** ITS#8671 - libldap - ldap_init_fd() in ldap.h (has patch, for Samba project, IPR OK) **** ITS#8674 - libldap - Fix leak (has patch, IPR not needed) ITS#8695 - slapd - "sleep" is deprecated (WINDOWS ONLY) (has patch, IPR OK) ITS#8754 - libldap - Correctly ignore IPv6 if IPv6 is disabled (has patch) **** ITS#8755 - libldap - leaking file descriptor when closing connection (has patch, IPR OK) ITS#8794 - libraries/libldap - Fix implicit declaration (has minor patch) **** ITS#8841 - back-meta - Fix assertion if the network interface goes down (17f1e32b65c332f7a33b77ebe6e20b47188a88aa) **** ITS#8864 - liblber - fix ber_flush (fb49d486a35fd4b2e993398c1eea0c8f7bc6ac40) **** ITS#8997 - slapd-ldap - Fix segfault (Howard already wrote the patch, just needs to be committed) **** ITS#9001 - libraries/libldap - Use new Tavl bits to reduce search time (has patch, IPR OK) OpenLDAP related ITSes for RE25 ------------------------------- ITS#8875 - back-mdb - fix performance problems with large DIT and many aliases (has patch) --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

3 3

2.4.48
by Michael Ströder 04 Jun '19

04 Jun '19

HI! Any blockers for releasing 2.4.48? Ciao, Michael.

2 1

Farewell BerkeleyDB we hardly knew ye
by Quanah Gibson-Mount 13 May '19

13 May '19

As of today, the two BerkeleyDB based backends (back-bdb, back-hdb) are removed from OpenLDAP head as part of the preparations for OpenLDAP 2.5. RIP! --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

anyone on this list who might have a contact for the LDAP Tool Box (LTB) mailing lists?
by Brian Reichert 10 May '19

10 May '19

I apologize for utilizing this forum for this, but does anyone here have contact with someone who runs the LDAP Tool Box (LTB) mailing lists? Please contact me off-list; I'm having difficulty getting mail delivered to the LTB mail server. -- Brian Reichert <reichert(a)numachi.com> BSD admin/developer at large

3 2

ITS#7770 and test056
by Quanah Gibson-Mount 03 May '19

03 May '19

In looking at test056, which specifically queries the BDB based attributes from back-monitor (olmBDBEntryCache olmBDBDNCache olmBDBIDLCache), shouldn't it be updated to do something similar for back-mdb's monitored attributes? olmMDBPagesMax olmMDBPagesUsed olmMDBPagesFree olmMDBReadersMax olmMDBReadersUsed olmDbDirectory --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Generating contextCSN on a newly adopted DB
by Ondřej Kuzník 25 Apr '19

25 Apr '19

Dealing with ITS#9015 has lead me to question part of the ITS#8281 fix in cd8ff37629012c1676ef79de164a159da9b2ae89 - the part that refuses to generate a contextCSN on a DB without one. When syncprov is adopting a database that has never been managed by it, it will only generate a new contexCSN if it's a standalone master (its serverID is zero and replicates from noone). But people can and do add a new database on a multimaster node expecting things to work OK, not something that happens now, even worse, we can lie to the consumer and say the DB is empty just because its contextCSN is. AFAIK, the root cause of ITS#8281 (as reported) was diagnosed to be two servers with the same serverID - not something we can or want to support. So my reaction is to make sure we always have a contextCSN (doesn't have to contain our own serverID yet), generating it if not unless we're running with SLAP_SINGLE_SHADOW(be) which means we might be a cascading replica. Is there a scenario that would break things? How about starting with an empty DB, should we still put a contextCSN there? Thanks, -- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP

1 0

Re: ITS 8996
by Hugh McMaster 23 Apr '19

23 Apr '19

Hi Quanah, On Sun, 21 Apr 2019 at 8:26 am, Quanah Gibson-Mount wrote: > As it is a feature request and not a bug fix, it may be a while as we're > currently working on getting the OpenLDAP 2.4 series (feature frozen) > wrapped up. At that point we can spend a bit more time on planning what > open feature requests will make their way into the next release series > (2.5). Thank you for the update. I had no idea the project was in a feature freeze, as the information doesn’t seem to be anywhere on the website. On that point, are there any plans/ideas to move to bugzilla or even github/gitlab for development? The ITS isn’t the most user friendly platform around. > Hugh

2 1

ITS 8996
by Hugh McMaster 21 Apr '19

21 Apr '19

Hi, I submitted #8996 [1] a month ago. I'm just wondering how long it will stay in Incoming before being reviewed and/or processed. Thank you, Hugh [1] http://www.openldap.org/its/index.cgi/Incoming?id=8996;page=29

2 1

need info for bug #955210: patch for openldap2 package
by Michael Ströder 19 Apr '19

19 Apr '19

HI! Please Cc: openldap-devel(a)openldap.org when replying. I need more information about this locked bug report: https://bugzilla.opensuse.org/show_bug.cgi?id=955210 The bug is referenced in openldap2.changes for this patch: https://build.opensuse.org/package/view_file/network:ldap/openldap2/0009-Fi… OpenLDAP upstream (Cc:-ed) asks whether SUSE folks could file an upstream issue here: https://www.openldap.org/its/ Upstream requires an IPR notice when submitting patches as described here: https://www.openldap.org/devel/contributing.html#notice Thanks in advance. Ciao, Michael.

1 0

← Newer
1
...
7
8
9
10
11
12
13
...
142
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-devel