summaryrefslogtreecommitdiffstats
path: root/ldap/synctools/passwordsync/passsync/syncserv.cpp
diff options
context:
space:
mode:
authorRich Megginson <rmeggins@redhat.com>2005-08-30 21:16:14 +0000
committerRich Megginson <rmeggins@redhat.com>2005-08-30 21:16:14 +0000
commit58c95dabe1332978130bd84fc1be6c9e6d115dab (patch)
treee46931ff2889f299e29810d7fe4d5fad949841b7 /ldap/synctools/passwordsync/passsync/syncserv.cpp
parentc72153219b031c39b339c96904b8dcedeea7d485 (diff)
Bug(s) fixed: 165641
Bug Description: ./ns-slapd crashes on bind containing invalid dn and password Reviewed by: Noriko (Thanks!) Branch: Directory71RtmBranch Fix Description: It's really crashing on the search request. The problem is that the server assumes all strings are encoded in utf8 format, since that is the only encoding allowed by the LDAP standards. Non-utf8 works in most places except the function slapi_utf8StrToLower(), which returns NULL given a string of non-utf8 bytes. The fix for this particular problem is to check for a NULL return value and handle accordingly. The real solution to this problem would be for the server to check for valid utf8 strings in _all_ LDAP data, according to the syntax of the attribute (e.g. for binary or octet string syntax data, and other binary formats, all bets are off, but then we shouldn't be doing strtolower on these blobs either). And, while we're at it, add data validation based on syntax for _all_ attributes e.g. in a pre-op. Platforms tested: RHEL4 Flag Day: no Doc impact: no QA impact: should be covered by regular nightly and manual testing New Tests integrated into TET: none
Diffstat (limited to 'ldap/synctools/passwordsync/passsync/syncserv.cpp')
0 files changed, 0 insertions, 0 deletions