summaryrefslogtreecommitdiffstats
path: root/ldap/admin/src/scripts/50faxsyntaxplugin.ldif
diff options
context:
space:
mode:
authorRich Megginson <rmeggins@redhat.com>2010-01-26 09:51:05 -0700
committerRich Megginson <rmeggins@redhat.com>2010-01-26 10:04:08 -0700
commit73fdd3b8945a34cc3d386c697e4e99560ba7997a (patch)
tree0f736da917e6dd5423b8990e905235f1aef42b6e /ldap/admin/src/scripts/50faxsyntaxplugin.ldif
parent9b38ac3b5d27014c072cffb5a83e5888689c411b (diff)
Bug 543080 - Bitwise plugin fails to return the exact matched entries for Bitwise search filter
https://bugzilla.redhat.com/show_bug.cgi?id=543080 Resolves: bug 543080 Bug Description: Bitwise plugin fails to return the exact matched entries for Bitwise search filter Reviewed by: nhosoi (Thanks!) Branch: HEAD Fix Description: The Microsoft Windows AD bitwise filters do not work exactly like the usual bitwise AND (&) and OR (|) operators. For the AND case the matching rule is true only if all bits from the value given in the filter value match the value from the entry. For the OR case, the matching rule is true if any bits from the value given in the filter match the value from the entry. For the AND case, this means that even though (a & b) is True, if (a & b) != b, the matching rule will return False. For the OR case, this means that even though (a | b) is True, this may be because there are bits in a. But we only care about bits in a that are also in b. So we do (a & b) - this will return what we want, which is to return True if any of the bits in b are also in a. Platforms tested: RHEL5 x86_64 Flag Day: no Doc impact: no
Diffstat (limited to 'ldap/admin/src/scripts/50faxsyntaxplugin.ldif')
0 files changed, 0 insertions, 0 deletions