If we follow RFC 2252 (ldapv3), DESC, defined as a qdstring, should not be an empty string, it should contain at least 1 UTF-8 character :
AttributeTypeDescription = "(" whsp
[...] [ "DESC" qdstring ] ; description
With qdstring defined as such : qdstring = whsp "'" dstring "'" whsp whsp = [ space ] space = 1" " dstring = 1utf8 utf8 = <any sequence of octets formed from the UTF-8 [9] transformation of a character from ISO10646 [10]>
From RFC 0822, 1*<element>, from REPETITION rule, is "requires at least one"
This is allegedly breaking interaction with applications using Microsoft LDAP APIs, in the following file : /etc/dirsrv/schema/50ns-mail.ldif
But egrep'ing for "DESC +*" gives me 84 results in 389-ds git repo, so there would be other files to patch.
attachment 0001-Ticket-47376-DESC-should-not-be-empty-as-per-RFC-225.patch
Do the official schemas have "real" descriptions? For example, I would expect the qmail and radius schemas to be officially defined somewhere with "real" descriptions?
Replying to [comment:4 rmeggins]:
I couldn't find anything for qmail attribute descriptions. As for the radius schema, Novell seems to be the only one who has descriptions for the radius schema. However, I'm not sure if I can legally use it. There is a copyright on the last page of this site:
http://www.novell.com/documentation//edir_radius/radiusadmin/?page=/documentation//edir_radius/radiusadmin/data/bv8m2ll.html
git merge ticket47376 Updating 944f7cd..9f73f01 Fast-forward ldap/schema/50ns-mail.ldif | 10 ++-- ldap/schema/60qmail.ldif | 20 +++--- ldap/schema/60radius.ldif | 132 ++++++++++++++++++++++---------------------- ldap/schema/60samba3.ldif | 2 +- 4 files changed, 82 insertions(+), 82 deletions(-)
git push origin master 944f7cd..9f73f01 master -> master
commit 9f73f01 Author: Mark Reynolds mreynolds@redhat.com Date: Fri Jun 7 14:48:07 2013 -0400
1.3.1
188fbd9..75a40e8 389-ds-base-1.3.1 -> 389-ds-base-1.3.1
1.3.0
e57be70..e05c7b4 389-ds-base-1.3.0 -> 389-ds-base-1.3.0
1.2.11
01f7e5b..4a29fe1 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
60upgradeschemafiles.pl should also be changed, see ticket 47861
Replying to [comment:8 lkrispen]:
Hi Ludwig, Could you elaborate your comment a little more? Are you suggesting to reopen this ticket for 1.2.11.x? Or ticket 47861's milestone has to be changed to 1.2.11.x? Or something else? Thanks! --noriko
Sorry for teh confusion, it was just a hint for Mark when fixing 47861, but Mark has doen a more thourough search and did catch this anyway, so just to be ignored
Got it. So, we are all good now. Thanks, Ludwig and Mark!
Metadata Update from @lkrispen: - Issue assigned to mreynolds - Issue set to the milestone: 1.2.11.22
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/713
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.