|
https://fedorahosted.org/389/ticket/48234 #48234: "matching rules" in ACI's "bind rules not fully evaluated https://fedorahosted.org/389/attachment/ticket/48234/0001-Ticket-48234-matching-rules-in-ACI-s-bind-rules-not-.patch git patch file (master) https://fedorahosted.org/389/attachment/ticket/48234/0002-Ticket-48234-CI-test-test-case-for-ticket-48234.patch git patch file (master) -- CI test https://fedorahosted.org/389/ticket/48848 #48848: modrdn deleteoldrdn can fail to find old attribute value, perhaps due to case folding https://fedorahosted.org/389/attachment/ticket/48848/0001-Ticket-48848-modrdn-deleteoldrdn-can-fail-to-find-ol.patch https://fedorahosted.org/389/ticket/48833 #48833: 389 showing inconsistent values for shadowMax and shadowWarning in 1.3.5.1 We need to choose one of these 2 solutions. Which would be preferable? https://fedorahosted.org/389/attachment/ticket/48833/0001-Ticket-48833-389-showing-inconsistent-values-for-sha.patch git patch file (master) -- first proposal -- if an entry has shadow values, they are not modified. https://fedorahosted.org/389/attachment/ticket/48833/0001-Ticket-48833-389-showing-inconsistent-values-for-sha.2.patch git patch file (master) -- second proposal -- even if an entry has shadow values, they are synchronized with the password policy values. To store 99999 days in seconds, internal password policy variables are switched to 64-bit. |
-- 389-devel mailing list 389-devel@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/389-devel@xxxxxxxxxxxxxxxxxxxxxxx
