Howard Chu wrote:
Howard Chu wrote:
Michael Ströder wrote:
But then I would expect slapd to remove the backslash(es) used for quoting:
Good point. OK, there's some more work needed in here somewhere.
Fixed. Closing this ITS. If you have any other problems regarding this, followup to ITS#8233. We don't open new ITSs for unreleased code.
Sorry, but still I see the same problem with commit 23953716c76ab36fab7d5f6dea335bf9bdea6323.
Example from ITS#8251 repeated here:
In slapd.conf:
---------------------------------- snip ---------------------------------- attributetype ( 1.3.6.1.4.1.5427.1.389.42.3 DESC 'Test attribute type with "double quotes" in DESC' SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 ) ---------------------------------- snip ----------------------------------
Returned via LDAP in subschema subentry (as LDIF):
---------------------------------- snip ---------------------------------- attributeTypes: ( 1.3.6.1.4.1.5427.1.389.42.3 DESC 'Test attribute type with "double quotes" in DESC' SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 ) ---------------------------------- snip ----------------------------------
But regarding your comment in [1] I wonder what counts as an "argument"? Reading the section slapd.conf(5) more carefully it could mean that also all schema descriptions (containing spaces) count as one argument and therefore should be enclosed in double quotes (which is not the case also for all .schema files installed by OpenLDAP).
Another example is:
index foo,bar eq,sub
Does the the config parser handle "foo,bar" and "eq,sub" as two separate arguments for directive "index"? Does the argument parsing depend on the configuration directive?
[1] https://www.openldap.org/its/index.cgi?findid=8251#followup9
Ciao, Michael.