Re: (ITS#9150) olcDbNoSync: FALSE has the same effect as olcDbNoSync: TRUE

2020-01-10 Thread hyc
maxime.bes...@worteks.com wrote: > Full_Name: Maxime Besson > Version: 2.4.48 > OS: Debian Buster / CentOS7 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (2a01:cb00:802:8400:2cbe:3c60:fca6:e50b) > > > While migrating configuration from slapd.conf to cn=config, I noticed >

Re: (ITS#9147) syncrepl connexion leak when provider uses an expired certificate

2020-01-10 Thread hyc
maxime.bes...@worteks.com wrote: > Full_Name: Maxime Besson > Version: 2.4.48 > OS: Debian Buster / CentOS7 > URL: https://cloud.worteks.com/index.php/s/9CE6ALLaAfrxZW4/download > Submission from: (NULL) (92.184.104.113) Thanks for the report and testcase, fixed now in git master. > > > I have

Re: (ITS#9124) CVE-ID?

2020-01-10 Thread michael
On 1/10/20 2:28 PM, Stephan Zeisberg wrote: > So far I have not requested a CVE-Id for the issue. That's what Howard > wrote in this regard: > >> Usual practice for CVEs is not to make them public until fixes are >> released. In the future, you should tick the Major Security Issue >> button for

Re: (ITS#9124) CVE-ID?

2020-01-10 Thread stephan
--_000_e1c562ac33aa2ed6c8e93818cf4da3fasrlabsde_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGkgTWljaGFlbCDigJQNCg0KU28gZmFyIEkgaGF2ZSBub3QgcmVxdWVzdGVkIGEgQ1ZFLUlkIGZv ciB0aGUgaXNzdWUuIFRoYXQncyB3aGF0IEhvd2FyZCB3cm90ZSBpbiB0aGlzIHJlZ2FyZDoNCg0K

Re: (ITS#9124) CVE-ID?

2020-01-10 Thread michael
Stephan, regarding: https://www.openldap.org/its/index.cgi?findid=9124 Was there ever a CVE-Id assigned to this issue? I'd like to reference it in back-port patches for downstream packages. Ciao, Michael.

Re: (ITS#9098) assert fails in meta_back_search in some cases after reconnect

2020-01-10 Thread maxime . besson
Hi, After a couple of months without any issues using 2.4.48, we suddenly encountered a crash again, but this time on 2.4.48. It was the exact same symptom, and the same assert failing as in my original message. It appears that the issue happens a lot more rarely in 2.4.48 compared to 2.4.47, so