slapd.config infinite loop

[Tristan Hill]

slapd_2.1.30-2

The query_initial_config function will only terminate if validate_initial_config
is true. If you do something silly like put a _ in the domain the function
will infinite loop (if in DEBIAN_FRONTEND=noninteractive mode)

[Dennis Kaarsemaker (dennis)]

Is this bug still present in Breezy/Dapper?

[Tristan Hill (stan)]

(In reply to comment #1)
> Is this bug still present in Breezy/Dapper?

Appears to be

Reproduce with
# export DEBIAN_FRONTEND=noninteractive
# export DEBCONF_DEBUG=developer
# dpkg --purge slapd
# echo slapd slapd/domain string _ | debconf-set-selections
# apt-get install slapd
<spin>

Some possibilities:
 * Add "_" to the regex (any other characters missing?) - not even sure "_" is valid
 * Add [ "$DEBIAN_FRONTEND" == "noninteractive" ] && db_set slapd/domain
nodomain in a relevant place
 * Set the default for slapd/invalid_config to false in the template

[Jonathan Anderson (jonathan-anderson)]

Confirmed in Dapper.

[Jonathan Anderson (jonathan-anderson)]

Also, I don't see this problem in Debian Sarge.

[JC Hulce (soaringsky)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.

[JC Hulce (soaringsky)]

Dapper is EOL, closing this bug.

[Tristan Hill (stan)]

still reproducible with slapd from precise following steps in #2

[JC Hulce (soaringsky)]

Thank you, reopened.

[Tristan Hill (stan)]

I think the package is slapd, now source package openldap. AFAIK openldap2.2 no longer exists - so openldap2.2 invalid/won't fix status is probably correct.