https://bugs.openldap.org/show_bug.cgi?id=7926
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |TEST
Keywords|OL_2_5_REQ |
Status|CONFIRMED |RESOLVED
--- Comment #3 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• 2f94318f
by Howard Chu at 2020-08-18T22:00:58+01:00
ITS#7926 support multiple config cleanup functions per op
Prep for main changes
• 9d2f1530
by Howard Chu at 2020-08-18T22:37:50+01:00
ITS#7926 dynamic changes to olcListenerThreads
Reallocates sockets from old to new listener threads
--
You are receiving this mail because:
You are on the CC list for the issue.
In our last blog we discussed the UGC NET JRF Eligibility Criteria (UGC NET JRF Admit Card, Eligibility Criteria & Exam Result).
Hence the checklist for you to know your eligibility, let’s discuss the checklist of the UGC NET JRF exam that checks your efficiency.
<a href="https://www.anujjindal.in/ugc-net-apply-online-syllabus-selection-criteria/">UGC NET JRF Selection Criteria</a>
https://bugs.openldap.org/show_bug.cgi?id=9135
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|OL_2_5_REQ |
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9135
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |TEST
--- Comment #2 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• b0d73083
by Howard Chu at 2020-08-13T18:18:45+01:00
ITS#9135 fix index error on collapsed range
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9135
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Howard Chu <hyc(a)openldap.org> ---
(In reply to Konstantin Andreev from comment #0)
> Full_Name: Konstantin Andreev
> Version: 2.4.48, git/master/44a7b46/20191203
> OS: Solaris 11.3 x64
> URL:
> Submission from: (NULL) (79.135.238.172)
>
>
> Here is a test case.
>
> 1) choose an attribute that has an equality index in your dit;
>
> 2) for this attribute choose a value that does not (and did not) exist in
> the dit yet;
>
> Let assume you chose [o=1] attr/val pair.
>
> 3) add MDB_IDL_DB_MAX+1 ( = 0x10000 = 65536 ) entries having [o=1]
> attr/val
> pair.
>
> 4) delete last MDB_IDL_DB_MAX-1 of them in the order inverted as
> compared to
> the order of addition
>
> Now you have two entries having [o=1] attr/val pair. Let assume they are
>
> | $ ldapsearch -s sub -b 'ou=T' '(o=1)' o
> | dn: cn=1,ou=T
> | o: 1
> |
> | dn: cn=2,ou=T
> | o: 1
>
> 5) delete one of the remaining entries, e.g. cn=2,ou=T
>
> Repeat the search:
>
> | $ ldapsearch -s sub -b 'ou=T' '(o=1)' o
> | $
>
> Nope, the remaining entry has been lost from the index forever. But it is
> still
> in the dit:
>
> | $ ldapsearch -s one -b 'ou=T' '(objectclass=*)' o
> | dn: cn=1,ou=T
> | o: 1
> |
> | dn: ou=A,ou=T
> | ...
>
> You need to slapindex to restore `o' index to a valid state, but you may not
> know you need to repair the index.
>
> The probability of this scenario is negligible, because indexed entries never
> form continuous block of ids of many-thousand length, but the code for this
> scenario exists and has a bug.
Thanks for the report. Fixed now in master.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9312
Issue ID: 9312
Summary: Getting connection_read(23): no connection!
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: ---
Hi,
I have a connection_read(23): no connection! message in my syslog.
This does not affect the functionality of anything on system but is simply
present in the logs.
Also, it comes randomly. No wrong password error or no such issues.
I have referred the ID's - 8781 and 6548.
But it does not help.
Secondly, I have updated the consolidated patch for the openldap version from
the openldap/patches website. that too does not help.
We want to know why this messages come in the logs ?
Regarding, This commonly occurs when a client ends the connection
without properly ending an unbind request first. The solution would be to
fix the client involved.
-- What does the client server need to do here ? I mean what is to be handled
correctly ? Is there any configuration miss ?
Awaiting your response.
- Shaheena K
--
You are receiving this mail because:
You are on the CC list for the issue.
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.
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>
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.
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.
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.
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.
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.
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.
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.
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.
https://bugs.openldap.org/show_bug.cgi?id=9301
Issue ID: 9301
Summary: Building OpenLDAP on Silicon (ARM) Mac
Product: OpenLDAP
Version: unspecified
Hardware: Other
OS: Mac OS
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: build
Assignee: bugs(a)openldap.org
Reporter: nicolas.brachfogel(a)4d.com
Target Milestone: ---
There's currently no target to build OpenLDAP on the new Apple Silicon (ARM)
Macs.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6467
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|IN_PROGRESS |RESOLVED
Resolution|--- |TEST
Keywords|OL_2_5_REQ |
--- Comment #6 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• 66a743f1
by Ondřej Kuzník at 2020-07-22T22:25:10+01:00
ITS#6467 Record minCSN in audit container
• 43ebfa8f
by Ondřej Kuzník at 2020-07-22T22:25:10+01:00
ITS#6467 Make accesslog a possible sessionlog source
• ee79cb38
by Ondřej Kuzník at 2020-07-22T22:25:10+01:00
ITS#6467 Add test script
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8645
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Keywords|OL_2_5_REQ |
Resolution|--- |TEST
--- Comment #1 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• 4b62f3b8
by Ondřej Kuzník at 2020-07-22T20:22:50+00:00
ITS#8645 Check for all syncrepl errors
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9098
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|2.4.51 |2.4.52
--- Comment #19 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Going to move this to a target of 2.4.52. We will be trying to reproduce this
internally with some new hardware we've acquired.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8511
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Rename "mirrormode" to |Rename "mirrormode" to
|"multimaster", deprecate |"multiprovider", deprecate
|"mirrormode" parameter |"mirrormode" parameter
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8511
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|has_patch, IPR_OK, |
|OL_2_5_REQ, |
|openldap-scratch |
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8511
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|IN_PROGRESS |RESOLVED
Resolution|--- |TEST
--- Comment #8 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• 3716245f
by Quanah Gibson-Mount at 2020-07-22T19:32:49+00:00
Issue#8511 - Update documentation and configs to correctly use multiprovider
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9121
--- Comment #6 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• 9210ed16
by Howard Chu at 2020-07-22T15:11:24+00:00
ITS#9121 add dynamic memberOf support for static groups
• 2c0499ae
by Howard Chu at 2020-07-22T15:11:24+00:00
ITS#9121 support nested groups
• c470af37
by Howard Chu at 2020-07-22T15:11:24+00:00
ITS#9121 add examples to manpage
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8619
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
--
You are receiving this mail because:
You are on the CC list for the issue.