You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously, storage nodes calculated action for eACL with numeric rules
incorrectly. This was caused by inverted comparison of filter and object
header values. For example, if rule is applied only to 'attr < 0',
the rule was applied to objects with 'attr = 1' and not applied to
objects with 'attr = -1'.
Now condition is inverted and numeric rules are matched correctly.
Fixes#2785. Refs #2742.
Signed-off-by: Leonard Lyubich <leonard@morphbits.io>
Expected Behavior
Get object with numeric_value=1 should be allowed with --rule 'deny get obj:numeric_value<0 user'
Current Behavior
Get object with numeric_value=1 is not allowed with --rule 'deny get obj:numeric_value<0 user'
The text was updated successfully, but these errors were encountered: