According to http://www.ietf.org/rfc/rfc4511.txt, the server should return unavailableCriticalExtension when receiving a badly formed critical control (null length or/and null value). Currently the return value is always protocol error whatever the critical flag is true/fals
attachment 0001-Ticket-600-Server-should-return-unavailableCriticalE.patch
attachment Makefile
'''Git merge+push''' (note I used new_branch_name to work on ticket600)
git merge new_branch_name Updating 41d95f8..e84c63f Fast-forward ldap/servers/plugins/acl/acleffectiverights.c | 29 ++++++++++++++++++----- ldap/servers/plugins/chainingdb/cb_utils.c | 15 +++++++++--- ldap/servers/plugins/deref/deref.c | 11 +++++++++ ldap/servers/slapd/back-ldbm/ldbm_search.c | 101 ++++++++++++++++++++++++++++++++++++++++++++++++++++++------------------------ ldap/servers/slapd/opshared.c | 12 +++++++--- ldap/servers/slapd/proxyauth.c | 13 +++++++--- 6 files changed, 135 insertions(+), 46 deletions(-)
git push origin master Counting objects: 31, done. Delta compression using up to 4 threads. Compressing objects: 100% (16/16), done. Writing objects: 100% (16/16), 3.18 KiB, done. Total 16 (delta 13), reused 0 (delta 0) To ssh://git.fedorahosted.org/git/389/ds.git 41d95f8..e84c63f master -> master
commit e84c63f Author: Thierry bordaz (tbordaz) tbordaz@redhat.com Date: Tue Mar 12 10:41:14 2013 +0100
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=947243
attachment search_critical_ctl.c
attachment search_critical_ctl
Metadata Update from @tbordaz: - Issue assigned to tbordaz - Issue set to the milestone: 1.3.1
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/600
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.