openldap-bugs

openldap-bugs@openldap.org

1 participants
20966 discussions

[Issue 5971] back-ldap: Referral chasing is broken
by openldap-its＠openldap.org 03 Jun '21

03 Jun '21

https://bugs.openldap.org/show_bug.cgi?id=5971 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|slapd |backends Summary|Referral chasing is broken |back-ldap: Referral chasing | |is broken -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 5971] Referral chasing is broken
by openldap-its＠openldap.org 03 Jun '21

03 Jun '21

https://bugs.openldap.org/show_bug.cgi?id=5971 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Debug mode "fixes" |Referral chasing is broken |authentication issue | -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 5919] URI syntaxe (ldap:///dc=my%2cdc=domaine)
by openldap-its＠openldap.org 03 Jun '21

03 Jun '21

https://bugs.openldap.org/show_bug.cgi?id=5919 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |enhancement -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 5582] Default OpenSSL certs are only used when TLS_CACERT(DIR)
by openldap-its＠openldap.org 03 Jun '21

03 Jun '21

https://bugs.openldap.org/show_bug.cgi?id=5582 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs(a)openldap.org |hyc(a)openldap.org Keywords|OL_2_6_REQ | -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 5399] LDAP Syntax 1.3.6.1.4.1.1466.115.121.1.58 (Substring Assertion) not listed in subschema subentry
by openldap-its＠openldap.org 03 Jun '21

03 Jun '21

https://bugs.openldap.org/show_bug.cgi?id=5399 --- Comment #8 from Quanah Gibson-Mount <quanah(a)openldap.org> --- Hi Michael, Do you have an example test case/use case you can provide? -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 5500] comments in cn=config entries
by openldap-its＠openldap.org 03 Jun '21

03 Jun '21

https://bugs.openldap.org/show_bug.cgi?id=5500 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |enhancement Target Milestone|2.6.0 |--- -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 5399] LDAP Syntax 1.3.6.1.4.1.1466.115.121.1.58 (Substring Assertion) not listed in subschema subentry
by openldap-its＠openldap.org 03 Jun '21

03 Jun '21

https://bugs.openldap.org/show_bug.cgi?id=5399 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |enhancement -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 5344] Wrong check for bad Modify DN
by openldap-its＠openldap.org 03 Jun '21

03 Jun '21

https://bugs.openldap.org/show_bug.cgi?id=5344 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs(a)openldap.org |ondra(a)mistotebe.net Keywords|OL_2_6_REQ | -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 5335] Update test044 to confirm ACL with "by group.X" clause using a dynamic group functions correctly
by openldap-its＠openldap.org 03 Jun '21

03 Jun '21

https://bugs.openldap.org/show_bug.cgi?id=5335 Quanah Gibson-Mount <quanah(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|2.6.0 |--- Keywords|OL_2_6_REQ | -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 7853] Improve safety of mdb_env_close
by openldap-its＠openldap.org 03 Jun '21

03 Jun '21

https://bugs.openldap.org/show_bug.cgi?id=7853 --- Comment #5 from Howard Chu <hyc(a)openldap.org> --- (In reply to Howard Chu from comment #4) > (In reply to dw(a)hmmz.org from comment #0) > > Full_Name: David Wilson > > Version: LMDB 0.9.11 > > OS: > > URL: > > https://raw.githubusercontent.com/dw/py-lmdb/master/misc/readers_mrb_env. > > patch > > Submission from: (NULL) (178.238.153.20) > > > > > > Currently if a user (wilfully or accidentally, say, through composition of > > third party libs) opens the same LMDB environment twice within a process, and > > maintains active read transactions at the time one mdb_env_close() is called, > > all reader slots will be deallocated in all environments due to the logic > > around line 4253 that unconditionally clears reader slots based on PID. > > > > I'd like to avoid this in py-lmdb, and seems there are a few alternatives to > > fix it: > > > 4) Modify lock.mdb to include MDB_env* address within the process, and update > > mdb_env_close() to invalidate only readers associated with the environment > > being closed. I dislike using the MDB_env* as an opaque publicly visible > > cookie, but perhaps storing this field might be reused for other things in > > future. > > I was looking at this approach, which initially seems harmless. But > unfortunately it does nothing to address the fact the fcntl lock on the > lock file will still go away on the first env_close() call. If there are > no other processes with the env open, then the next process that opens > the env will re-init the lock file, because it doesn't know about the > existing process. At that point the existing process is hosed anyway. Another possibility here is to detect that there were multiple envs for the same PID, and not close the descriptors in that case. This means intentionally leaking a file descriptor, but keeps the locks intact. Still ugly, but not as bad as inviting corruption. And, this would only happen due to a library misuse, so it would still be a rare situation. -- 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