openldap-bugs

openldap-bugs@openldap.org

1 participants
21513 discussions

(ITS#5324) Access violation on Windows due to %n in format strings
by jeff.lewis＠teradata.com 10 Jan '08

10 Jan '08

Full_Name: Jeff Lewis Version: 2.3.20 OS: Microsoft Windows on IA64 URL: http://msdn2.microsoft.com/en-us/library/ms175782.aspx Submission from: (NULL) (192.127.94.7) We (Teradata, formerly NCR) have encountered a small glitch with the latest Windows SDK and OpenLDAP client tools. We're getting an access violation where we did not get one with the older SDK. Our IA64 builds require the newer SDK because of codegen issues with the older compilers...but soon, we're going to be moving to the newer SDK for i386 and x8664 so the problem will begin to crop up there as well. Here's the problem: In libraries/libldap/url.c, function ldap_url_desc2str, there are a couple of sprintfs that use %n in their format strings to return position information. The latest Windows SDKs have heavily deprecated %n and its use now results in an unfortunate access violation and process crash. We've added a call to "_set_printf_count_output(1)" in libraries/libldap/init.c function ldap_int_initialize() to re-enable %n so we're sufficiently worked around for the moment. We're happy with our own workaround so we're not asking for any kind of quick turnaround on this issue. If you want to fix this, please do so in your own time and in your own way. You can consider this a courtesy report only. If you decide not to fix this, please let me know because we'll need to add a formal test case to our regression suites to make sure we don't resurrect the issue when we upgrade our OpenLDAP clients. The msdn.microsoft.com website has the details of their proprietary function and SDK versions where it's required in case you want to use our approach. I included the URL so that you can get to it directly without going through MSDN's searching. My own opinion is finding a way to do without the %n is probably better and would result in fewer ifdefs in the code (always a plus in my book) and less Microsoft specific code lurking around to bite us later. We did pull down 2.3.39 and our tech that looked at the code tells me the %n's are still there and there's no _set_printf_count_output call so we think the problem still exists in the latest version. Give me a virtual slap if I've got this wrong. If you decide to fix this, I'm at your disposal and can provide some testing support since IA64 platforms are pretty rare. If you want to get in touch with me and my email address doesn't work (we're in a spin-off transition right now so our infrastructure isn't as stable as it should be), you can reach me by phone at 310-616-2384.

1 0

Re: (ITS#5323) dyngroup.c:dgroup_cf() bug
by hyc＠symas.com 10 Jan '08

10 Jan '08

h.b.furuseth(a)usit.uio.no wrote: > I wrote: >> To avoid that, start the code with something like >> ap = on->on_bi.bi_private; >> app = ≈ > > Duh.. ignore that one. > Probably should ignore all of this. dynlist totally supersedes dyngroup now. -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#5323) dyngroup.c:dgroup_cf() bug
by h.b.furuseth＠usit.uio.no 10 Jan '08

10 Jan '08

I wrote: > To avoid that, start the code with something like > ap = on->on_bi.bi_private; > app = ≈ Duh.. ignore that one. -- Hallvard

1 0

(ITS#5323) dyngroup.c:dgroup_cf() bug
by h.b.furuseth＠usit.uio.no 10 Jan '08

10 Jan '08

Full_Name: Hallvard B Furuseth Version: HEAD, RE24 OS: URL: Submission from: (NULL) (129.240.6.233) Submitted by: hallvard overlays/dyngroup.c:dgroup_cf() has some strange LDAP_MOD_DELETE code: app = (adpair **)&on->on_bi.bi_private; for (...; ...; ..., app = &ap->ap_next) { ap = *app; } *app = ap->ap_next; Last statement is a no-op, since *app == *(&ap->ap_next) == ap->ap_next. I'm not sure what it's intended to do. Also the first statement makes the void* object bi_private be accessed as an adpair* object. Breaks the 'strict aliasing' rules, so I guess it can miscompile. To avoid that, start the code with something like ap = on->on_bi.bi_private; app = ≈

1 0

Re: (ITS#5321) slapindex fails to create cn=config from configuration file
by hyc＠symas.com 10 Jan '08

10 Jan '08

joshua(a)itsecureadmin.com wrote: > Quanah Gibson-Mount wrote: >> --On Thursday, January 10, 2008 9:09 PM +0000 joshua(a)itsecureadmin.com >>> Full_Name: Joshua Miller >>> Version: 2.4.7 >>> OS: CentOS 5 >>> URL: ftp://ftp.openldap.org/incoming/ >>> Submission from: (NULL) (198.134.96.10) >> What makes you think you should be using slapindex to do this? > > > The admin guide suggests that any slap* command should do this: > > http://www.openldap.org/doc/admin24/slapdconf2.html#cn=config > > > Also, the slapd-config man page: > > Alternatively, an existing slapd.conf file can be converted to > the new format using slapd or any of the slap tools: > slaptest -f /etc/openldap/slapd.conf -F ETCDIR/slapd.d The docs are incomplete. slapd or slaptest will always work; the other tools (slapadd/slapcat/slapindex) don't actually invoke the config database's startup routine unless you're explicitly operating on the config backend therefore the conversion won't occur in general. -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

(ITS#5322) slaptest exits on seg fault (SIGSEGV) if id2entry.bdb does not exist
by joshua＠itsecureadmin.com 10 Jan '08

10 Jan '08

Full_Name: Joshua Miller Version: 2.4.7 OS: CentOS 5 URL: http://ditree.com/work/gdb.ol2.4.7.out Submission from: (NULL) (198.134.96.10) When issuing slaptest prior to executing slapd to generate an id2entry.bdb file, slaptest/slapindex exits with a segmentation fault (SIGSEGV). Use case: user installs OpenLDAP, generates a configuration file, slapd.conf. User decides to generate cn=config prior to running slapd. User receives seg fault through running slaptest to perform this operation. Steps to reproduce: * install openldap 2.4.7, using berkley db 4.6 * create suitable slapd.conf * attempt to validate the configuration file using the following command: slaptest -f slapd.conf Expected results: Success Actual results: Segmentation Fault (SIGSEGV). Possibly useless gdb output located at: http://ditree.com/work/gdb.ol2.4.7.out

1 0

Re: (ITS#5321) slapindex fails to create cn=config from configuration file
by joshua＠itsecureadmin.com 10 Jan '08

10 Jan '08

Quanah Gibson-Mount wrote: > --On Thursday, January 10, 2008 9:09 PM +0000 joshua(a)itsecureadmin.com >> Full_Name: Joshua Miller >> Version: 2.4.7 >> OS: CentOS 5 >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (198.134.96.10) > > What makes you think you should be using slapindex to do this? The admin guide suggests that any slap* command should do this: http://www.openldap.org/doc/admin24/slapdconf2.html#cn=config Also, the slapd-config man page: Alternatively, an existing slapd.conf file can be converted to the new format using slapd or any of the slap tools: slaptest -f /etc/openldap/slapd.conf -F ETCDIR/slapd.d Thanks, -- Joshua M. Miller - RHCE,VCP

1 0

Re: (ITS#5321) slapindex fails to create cn=config from configuration file
by quanah＠zimbra.com 10 Jan '08

10 Jan '08

--On Thursday, January 10, 2008 9:09 PM +0000 joshua(a)itsecureadmin.com wrote: > Full_Name: Joshua Miller > Version: 2.4.7 > OS: CentOS 5 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (198.134.96.10) > > > OL Version 2.4.7 > Berkely DB 4.6 > OS CentOS 5 > > Command: slapindex What makes you think you should be using slapindex to do this? --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#5321) slapindex fails to create cn=config from configuration file
by joshua＠itsecureadmin.com 10 Jan '08

10 Jan '08

Full_Name: Joshua Miller Version: 2.4.7 OS: CentOS 5 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (198.134.96.10) OL Version 2.4.7 Berkely DB 4.6 OS CentOS 5 Command: slapindex ISSUE: When attempting to generate cn=config from a configuration file using slapindex, no cn=config is generated: # cd /etc/openldap # mkdir slapd.d # /usr/sbin/slapindex -f /etc/openldap/slapd.conf -F /etc/openldap/slapd.d # echo $? 0 Program exits without error. # ls /etc/openldap/slapd.d Subsequently, running this command immediately after generates the appropriate cn=config: # slaptest -f /etc/openldap/slapd.conf -F /etc/openldap/slapd.d config file testing succeeded # ll slapd.d total 8 drwxr-x--- 4 root root 4096 Jan 10 13:07 cn=config -rw------- 1 root root 1097 Jan 10 13:07 cn=config.ldif #

1 0

Re: (ITS#5320) bug on the filter functionnality =*
by quanah＠zimbra.com 10 Jan '08

10 Jan '08

--On Thursday, January 10, 2008 3:31 PM +0000 jpgressard(a)hotmail.com wrote: > I tested the same query on the version 2.4.6 and it was working. > Furthermore, if I amend the query to (&(sn=XXX*)(givenName=D*)), or > (sn=XXX*) I find the entry. As noted when 2.4.7 was released, you want to regenerate your indices. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs