Actions
Bug #5546
closedBug #5467: rules: more graceful handling of anomalies for stable versions
rules: don't error on bad hex in content
Affected Versions:
Effort:
Difficulty:
Label:
Description
In 6.0.6 the content parser started rejecting broken hex, but this causes issues in production.
Instead of failing to load rules with -T, we should warn by default and only fail if we add a special strict option.
Actions