https://bugs.openldap.org/show_bug.cgi?id=9509
Issue ID: 9509
Summary: ldap_pvt_tls_check_hostname missing prototype
Product: OpenLDAP
Version: 2.4.57
Hardware: Other
OS: Mac OS
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: libraries
Assignee: bugs(a)openldap.org
Reporter: noloader(a)gmail.com
Target Milestone: ---
Hi Everyone,
I'm building OpenLDAP 2.4.57 on Apple M1. Apple turned on -Werror for missing
prototypes. It results in:
tls2.c:378:9: error: implicit declaration of function
'ldap_pvt_tls_check_hostname' is invalid in C99
[-Werror,-Wimplicit-function-declaration]
err = ldap_pvt_tls_check_hostname( ld, ssl, host );
You can access an Apple M1 machine on the GCC Compile Farm. It is GCC304, port
2409. If needed you can get an account at
https://cfarm.tetaneutral.net/users/new/.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9508
Issue ID: 9508
Summary: Add support for maxentrysize for slapd-mdb
Product: OpenLDAP
Version: 2.5
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: backends
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
Symas has code to set a max entry size limitation on entries in back-mdb. This
code needs upstreaming for 2.5
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8707
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|2.5.3 |2.5.4
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8707
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|IN_PROGRESS |CONFIRMED
--- Comment #30 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
This patch is seriously deficient and will be rejected unless there is follow
up in the near future from the patch author.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8950
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|IN_PROGRESS |RESOLVED
Resolution|--- |TEST
--- Comment #5 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• c6e521fa
by Howard Chu at 2021-03-23T14:58:09+00:00
ITS#8950 move txn setup to frontend
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8668
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|2.5.3 |---
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=8668
--- Comment #4 from Howard Chu <hyc(a)openldap.org> ---
(In reply to Howard Chu from comment #3)
> I was able to reproduce the behavior, but there is no bug here.
>
> You're seeing the old entry because it's left over from a previous run of
> slapd.
> The pcache overlay will forget what it knows about the cache contents on a
> restart, unless you configure pcachePersist. When you enable this setting,
> then it remembers its cached queries across restarts and will expire old
> entries instead of returning them in new search requests.
To be clear: I could only reproduce this behavior if slapd was stopped and
restarted between queries:
1: perform a cacheable search
2: shutdown slapd and restart before cached query expires
3: move entry on remote server
4: repeat the cacheable search
5: repeat the cacheable search again
On step 1, pcache will query the remote and store a copy of the returned entry.
On step 2, the restart will make pcache forget it stored anything.
On step 4, pcache will query the remote server because it thinks its cache is
empty, and store and return the new result (only).
On step 5, pcache will serve the request entirely from cache, and return both
the old and new entries.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8668
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|UNCONFIRMED |RESOLVED
--- Comment #3 from Howard Chu <hyc(a)openldap.org> ---
I was able to reproduce the behavior, but there is no bug here.
You're seeing the old entry because it's left over from a previous run of
slapd.
The pcache overlay will forget what it knows about the cache contents on a
restart, unless you configure pcachePersist. When you enable this setting,
then it remembers its cached queries across restarts and will expire old
entries instead of returning them in new search requests.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9251
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|OL_2_5_REQ, reviewed |
--- Comment #8 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• f1ebb456
by Howard Chu at 2021-03-22T17:31:13+00:00
ITS#9251 make max filter depth configurable
--
You are receiving this mail because:
You are on the CC list for the issue.