openldap-bugs

openldap-bugs@openldap.org

1 participants
20985 discussions

[Issue 9313] New: TLS 1.3 Support on 2.4.44
by openldap-its＠openldap.org 11 Aug '20

11 Aug '20

https://bugs.openldap.org/show_bug.cgi?id=9313 Issue ID: 9313 Summary: TLS 1.3 Support on 2.4.44 Product: OpenLDAP Version: 2.4.44 Hardware: x86_64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: --- Component: slapd Assignee: bugs(a)openldap.org Reporter: shaheena.kazi(a)gmail.com Target Milestone: --- Hello, I wanted to know if TLSv1.3 is supported on openldap 2.4.44 If no, then what about on openldap 2.4.47 ? Awaiting your response. Regards, Shaheena K -- You are receiving this mail because: You are on the CC list for the issue.

1 3

Nabard Grade A Syllabus
by Anuj jindal 11 Aug '20

11 Aug '20

NABARD Grade A officer post is one such post which is a dream of a lot of people. You get to make policies for the backbone of the country “agriculture”. You can look at the job profile of a NABARD Grade A Officer. It is really interesting. The salary of a NABARD Grade A officer is good and its syllabus is similar to that of RBI & SEBI. You can go through NABARD Grade A salary here. In this blog, I’m essentially going to talk about five things: <a href="https://www.anujjindal.in/nabard-grade-a-selection-criteria-syllabus-cut-of…">NABARD Grade A Selection Criteria </a>

1 0

[Issue 9171] slapd with ppolicy and pwdAccountLockedTime crashes
by openldap-its＠openldap.org 10 Aug '20

10 Aug '20

https://bugs.openldap.org/show_bug.cgi?id=9171 Ondřej Kuzník <ondra(a)mistotebe.net> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.openldap.org/s | |how_bug.cgi?id=9309 -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 9299] New: Memory leaks in ldap_simple_bind_s
by openldap-its＠openldap.org 06 Aug '20

06 Aug '20

https://bugs.openldap.org/show_bug.cgi?id=9299 Issue ID: 9299 Summary: Memory leaks in ldap_simple_bind_s Product: OpenLDAP Version: 2.4.49 Hardware: x86_64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: --- Component: libraries Assignee: bugs(a)openldap.org Reporter: Ritu.Varkey(a)microfocus.com Target Milestone: --- Created attachment 747 --> https://bugs.openldap.org/attachment.cgi?id=747&action=edit Sample code with call to bind API The call to ldap_simple_bind_s API leaks memory. Even after calling ldap_unbind_s or ldap_unbind_ext memory is not getting freed. Our application uses this API every time we make a connection to the directory. The API is being used on Windows operating system. -- You are receiving this mail because: You are on the CC list for the issue.

1 9

[Issue 9085] Test suite is failing
by openldap-its＠openldap.org 04 Aug '20

04 Aug '20

https://bugs.openldap.org/show_bug.cgi?id=9085 --- Comment #3 from Quanah Gibson-Mount <quanah(a)openldap.org> --- (In reply to kloczko.tomasz(a)gmail.com from comment #2) > Could you please say a little more about what kind of "enviroment problem" > it could be? "Hangup" indicates your OS killed the process. You'll need to examine your system logs to determine why. -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 9085] Test suite is failing
by openldap-its＠openldap.org 01 Aug '20

01 Aug '20

https://bugs.openldap.org/show_bug.cgi?id=9085 --- Comment #2 from kloczko.tomasz(a)gmail.com <kloczko.tomasz(a)gmail.com> --- Could you please say a little more about what kind of "enviroment problem" it could be? -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 9291] New: Detection of corrupted database files
by openldap-its＠openldap.org 30 Jul '20

30 Jul '20

https://bugs.openldap.org/show_bug.cgi?id=9291 Issue ID: 9291 Summary: Detection of corrupted database files Product: LMDB Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: liblmdb Assignee: bugs(a)openldap.org Reporter: markus(a)objectbox.io Target Milestone: --- Let's assume we have to deal with a corrupted database for whatever reason (e.g. broken hardware or file system). Current behavior seems to be mostly undefined, which is understandable as it's not known what is broken (e.g. there are no checksums). For example, I'm seeing a SIGBUS in mdb_page_touch because the cursor's top page (mp) is pointing to invalid memory (0x7f99cf004000) during a commit: mdb_page_touch mdb.c:2772 mdb_page_search mdb.c:6595 mdb_freelist_save mdb.c:3575 mdb_txn_commit mdb.c:4060 Cursor data at that point: mc_snum = 1, mc_top = 0; myki[0] = 0 A SIGBUS is troublesome as it crashes the process, and I wonder if there are other ways to detect such inconsistencies. If that be possible there could be user-specific handling in place. E.g. a user might start a new database file. This issue was reported by our users, which also provided DB files: https://github.com/objectbox/objectbox-java/issues/859 I did not find a lot of consistency checks besides MDB_PAGE_NOTFOUND and MDB_CORRUPTED. Also, I think there's no current way to thoroughly check a DB file (e.g. like fsck for the DB file)? My first idea other than checksums was to walk through the branch pages from the root and check if the referenced pages are within reasonable bounds. Also check the page content (e.g. nodes, flags). Additionally (optionally?), it should be possible to check that the key values are actually sorted. So, it boils down to 3 points in summary: 1.) If there no way to check the DB file for consistency yet(?), which approach do you think would make sense? There might be two modes; one for a through check through all data, and a quick check that does not take long and could be e.g. done when opening the DB. Goal is to avoid process crashes and let users handle the situation. 2.) In general, is it possible to add more consistency checks in regular DB operations? 3.) Could the the particular situation (for which I provided the stack trace) detected (e.g. is myki[0] = 0 legal here?) I'd be happy to provide a patch if you provide some direction where you want to take that. -- You are receiving this mail because: You are on the CC list for the issue.

1 25

[Issue 8784] SIGBUS in mdb_page_touch
by openldap-its＠openldap.org 27 Jul '20

27 Jul '20

https://bugs.openldap.org/show_bug.cgi?id=8784 --- Comment #3 from Howard Chu <hyc(a)openldap.org> --- (In reply to stefan.penner from comment #2) > I realize this issue is rather old, but I have some related questions; > hopefully that is alright: > > * The reporter mentions Android 7, do we know if the problem is limited to > Android 7, or do other Androids also suffer from this issue? > * Was someone able to come up with a consistent reproduction? If so, could > it be shared or described? I'm not aware of any consistent reproducer. Also, haven't run into this in quite a while, possibly it was already fixed in Android 9 or so -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 8784] SIGBUS in mdb_page_touch
by openldap-its＠openldap.org 27 Jul '20

27 Jul '20

https://bugs.openldap.org/show_bug.cgi?id=8784 --- Comment #2 from stefan.penner(a)gmail.com --- I realize this issue is rather old, but I have some related questions; hopefully that is alright: * The reporter mentions Android 7, do we know if the problem is limited to Android 7, or do other Androids also suffer from this issue? * Was someone able to come up with a consistent reproduction? If so, could it be shared or described? -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 9266] Replace custom hostname and IP address verification with OpenSSL API
by openldap-its＠openldap.org 24 Jul '20

24 Jul '20

https://bugs.openldap.org/show_bug.cgi?id=9266 --- Comment #3 from Quanah Gibson-Mount <quanah(a)openldap.org> --- Also important to note that RFC6125 specifically states in section 1.4 that it does not apply to existing protocols, such as LDAP. It even calls this out in Appendix B, section B.3, that the LDAP protocol is *not* covered by this RFC. -- You are receiving this mail because: You are on the CC list for the issue.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs