https://bugs.openldap.org/show_bug.cgi?id=9859
Issue ID: 9859
Summary: fix test
Product: OpenLDAP
Version: 2.5.12
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: hamano(a)osstech.co.jp
Target Milestone: ---
Created attachment 904
--> https://bugs.openldap.org/attachment.cgi?id=904&action=edit
openldap-2.5-fix_test.patch
1. specifiy modulepath and moduleload
moduleload ../rel/mod.la works on build directry ex: make test
but it doesn't work with installed slapd.
It should be specified the modulepath and moduleload separately like other
tests.
```
modulepath ../servers/slapd/overlays/
moduleload mod.la
```
2. skip test020-proxycache for back-wt
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9799
Issue ID: 9799
Summary: Clearing pending ops on Bind
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: ondra(a)mistotebe.net
Target Milestone: ---
When slapd receives some operations before it has started processing a queued
bind, those get added into conn->c_ops_pending and c_n_pending_ops is updated
accordingly.
Bind then eventually invokes connection_abandon() which forgets to zero out
c_n_pending_ops and the connection remains unusable forever.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6461
OndÅ™ej KuznÃk <ondra(a)mistotebe.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|2.5.0 |2.5.12
Group|OpenLDAP-devs |
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9157
--- Comment #5 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
head:
• 2c0707cf
by Howard Chu
ITS#9157: check for NULL ld
RE26 (2.6.3):
• 6675535c
by Howard Chu at 2022-06-03T20:29:24+00:00
ITS#9157: check for NULL ld
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9020
--- Comment #6 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
head:
• 737bcd7f
by OndÅ™ej KuznÃk at 2022-06-03T16:52:37+00:00
ITS#9020 Reinstate olcAutomaticGroups and document its deprecation
RE26 (2.6.3):
• 4a755258
by OndÅ™ej KuznÃk at 2022-06-03T17:42:35+00:00
ITS#9020 Reinstate olcAutomaticGroups and document its deprecation
RE25 (2.5.13):
• 02ddd515
by OndÅ™ej KuznÃk at 2022-06-03T17:43:55+00:00
ITS#9020 Reinstate olcAutomaticGroups and document its deprecation
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9857
Issue ID: 9857
Summary: add password policy
Product: OpenLDAP
Version: 2.6.2
Hardware: x86_64
OS: Linux
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: overlays
Assignee: bugs(a)openldap.org
Reporter: elizabeth.real(a)jpl.nasa.gov
Target Milestone: ---
I'm upgrading from openldap 2.4 running on RHEL7 up to 2.6.2 and RHEL8 on new
hardware, apparently the way to configure password policy now is by configuring
the slapd.conf file rather than loading the ppolicy schema. How do I modify
that file properly? I read
https://www.openldap.org/doc/admin26/overlays.html#Password%20Policies
on section 12.10.2. Password Policy Configuration, what does it mean to
"Instantiate the module in the database"?
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9854
Issue ID: 9854
Summary: We are best digital marketing
Product: website
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: website
Assignee: bugs(a)openldap.org
Reporter: moldshilarious50(a)gmail.com
Target Milestone: ---
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9852
Issue ID: 9852
Summary: Error
Product: website
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: website
Assignee: bugs(a)openldap.org
Reporter: aarounsmind03(a)gmail.com
Target Milestone: ---
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9848
Issue ID: 9848
Summary: Test 022-ppolicy fails on master if slapd has only
--enable-overlays and --with-tls=openssl
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: dstoychev(a)symas.com
Target Milestone: ---
**Steps to reproduce:
- Checkout master
./configure --enable-overlays --with-tls=openssl
make depend
make
make test
**Current result:
Test fails, here is the output:
./run test022-ppolicy
Cleaning up test run directory leftover from previous run.
Running ./scripts/test022-ppolicy for mdb...
running defines.sh
Starting slapd on TCP/IP port 9011...
Using ldapsearch to check that slapd is running...
Testing redundant ppolicy instance...
Using ldapadd to populate the database...
Testing account lockout...
Waiting 13 seconds for lockout to reset...
Testing password expiration
Waiting 10 seconds for password to expire...
Resetting password to clear expired status
Filling password history...
Testing password history...
Testing failed logins when password/policy missing...
Testing forced reset...
Clearing forced reset...
Testing Safe modify...
Testing length requirement...
Testing hashed length requirement...
Testing multiple password add/modify checks...
Testing idle password expiration
Switching to a policy with idle expiration...
Waiting 15 seconds for password to expire...
Reverting to Standard policy...
Testing obsolete Netscape ppolicy controls...
Enabling Netscape controls...
Reconfiguring policy to remove grace logins...
ldapmodify failed (255)!
**Expected result:
Test passed
**Notes:
- Reproducible on master branch only.
- Same test passes on 2.6 branch (with the same slapd config)
- Test could pass on master if other "configure" options are enabled, so make
sure to use only "--enable-overlays" and "--with-tls=openssl" to reproduce
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7165
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|IN_PROGRESS |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
HEAD:
• 205e2f1a
by Howard Chu at 2022-05-16T13:54:08+00:00
ITS#7165 back-mdb: check for stale readers on MDB_READERS_FULL
RE26:
• 7e7f01c3
by Howard Chu at 2022-05-16T15:09:08+00:00
ITS#7165 back-mdb: check for stale readers on MDB_READERS_FULL
RE25:
• f3d89d62
by Howard Chu at 2022-05-16T15:11:51+00:00
ITS#7165 back-mdb: check for stale readers on MDB_READERS_FULL
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7165
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needs_review |
Target Milestone|--- |2.5.13
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9838
Issue ID: 9838
Summary: Add decoding of the RFC 4517 Postal Address format
Product: JLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: JDBC
Assignee: bugs(a)openldap.org
Reporter: fredrik(a)roubert.name
Target Milestone: ---
No software connecting to an LDAP database through JDBC can be expected to know
anything at all about LDAP, so no such software can be expected to be able to
decode the RFC 4517 Postal Address format (1.3.6.1.4.1.1466.115.121.1.41).
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7165
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|bugs(a)openldap.org |hyc(a)openldap.org
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7165
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|unspecified |2.4.47
Keywords| |needs_review
Product|LMDB |OpenLDAP
Component|liblmdb |backends
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9385
Issue ID: 9385
Summary: Opening an env with MDB_NOSUBDIR with no existing file
returns error
Product: LMDB
Version: unspecified
Hardware: All
OS: Mac OS
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: liblmdb
Assignee: bugs(a)openldap.org
Reporter: kriszyp(a)gmail.com
Target Milestone: ---
Created attachment 776
--> https://bugs.openldap.org/attachment.cgi?id=776&action=edit
A fix to tolerate stat call on non-existing file
Calling mdb_env_open with a file path to a file that doesn't exist yet, with
MDB_NOSUBDIR on a non-Windows OS will return an error indicating that the file
doesn't exist. This is supposed to create a new file, and works properly on the
mdb.master branch, and still functions properly on Windows. The error is due to
the stat() call in mdb_env_open prior to the file existing.
I attached a patch that tolerates the absence of the file before checking if
the file is on a block device. I am not sure if this is the appropriate fix, or
if would be better to move this check later in mdb_env_open after the file is
created, or alternately, determining the parent directory and calling stat on
that.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8165
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.
https://bugs.openldap.org/show_bug.cgi?id=7754
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |IN_PROGRESS
--- Comment #3 from Howard Chu <hyc(a)openldap.org> ---
mdb.master was changed long ago to pad odd-sized keys to fix this issue. Fix is
still unreleased due to the resulting on-disk format change.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7364
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |trivial
Priority|--- |Lowest
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7165
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |IN_PROGRESS
Ever confirmed|0 |1
--- Comment #6 from Howard Chu <hyc(a)openldap.org> ---
> At this point the only potential action I see is to add a check for
MDB_READERS_FULL as noted at the beginning of this reply.
https://git.openldap.org/openldap/openldap/-/merge_requests/526
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8165
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Howard Chu <hyc(a)openldap.org> ---
*** This issue has been marked as a duplicate of issue 7794 ***
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7794
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |quanah(a)openldap.org
--- Comment #2 from Howard Chu <hyc(a)openldap.org> ---
*** Issue 8165 has been marked as a duplicate of this issue. ***
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9839
Issue ID: 9839
Summary: Undocumented behavior of ldap_url_parse() when port is
0 in URL string
Product: OpenLDAP
Version: unspecified
Hardware: Other
OS: Other
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: documentation
Assignee: bugs(a)openldap.org
Reporter: jiaqing.zhao(a)linux.intel.com
Target Milestone: ---
In ldap_url_parse(), when the port in URL string is set to 0 like
"ldap://example.com:0", the output value of lud_port will be the default port
(389 for LDAP, 636 for LDAPs). This behavior is undocumented.
I created a patch to illustrate this behavior. As my gitlab account is pending
confirmation, I put it in the attachments.
This affects OpenLDAP 2.5.x and 2.6.x, but it is already been fixed in master
branch
https://git.openldap.org/openldap/openldap/-/commit/e3905c989821f6c09576988…
for issue #9596. Will it be included in 2.7.0? If so, I may need to add
something like "(Until OpenLDAP 2.7.0)" before the line I added.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8882
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|IN_PROGRESS |RESOLVED
--- Comment #16 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
head:
• d2057745
by OndÅ™ej KuznÃk at 2022-05-10T14:24:49+00:00
ITS#8882 Add slapo-emptyds to contrib
RE26:
• edc67c6d
by OndÅ™ej KuznÃk at 2022-05-12T15:45:18+00:00
ITS#8882 Add slapo-emptyds to contrib
RE25:
• 6c9cb00f
by OndÅ™ej KuznÃk at 2022-05-12T15:46:13+00:00
ITS#8882 Add slapo-emptyds to contrib
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9843
Issue ID: 9843
Summary: slapcat and slapadd have no -r option
Product: OpenLDAP
Version: 2.5.12
Hardware: All
OS: Linux
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: dpa-openldap(a)aegee.org
Target Milestone: ---
I run openldap in a chrooted environment, by calling
/usr/local/libexec/slapd -d0 -u openldap -r /home/openldap -F /etc/openldap/ -h
'ldap://zzz'
I want to migrate 2.5 → 2.6. The manual says first to call slapcat on the
databases. In the /home/openldap/etc/openldap directory are the configurations
of the databases. The path there:
olcDbDirectory: /var/openldap-data/yyy
obviously references the path within the chrooted environment, the path is
/home/openldap/var/openldap-data/yyy outside the chrooted environment.
Slapcat has no -r option. So there is no way to export the databases by using
slapcat -n 0 -F /home/openldap/etc/openldap/ . Strace(1) shows that the file
openat(AT_FDCWD, "/var/openldap-data/yyy/DUMMY"
is missing and the error message is
slapcat: bad configuration directory!
In fact there is a way: symlinking /var/openldap-data outside the chrooted
environment to /var/openldap-data inside the chrooted environment. This way
does work, but it requires expert magic like using strace.
Please add -r option to slapcat and slapadd, which performs chroot to the
directory, after opening the file specified by the -l parameter.
--
You are receiving this mail because:
You are on the CC list for the issue.