Ruleset sanity silently ignores unknown range

• Reporter: cazfi
• Owner: cazfi
• Type: Bugs
• Status: Closed
• Component: General
• MileStone: 3.0.4 (closed)
• Priority: 5 - Medium
• Severity: 5 - Medium
• Resolution: Fixed
• File: 2

Details

req_from_str() : "If no range is given a default fallback is used rather than giving an error." The problem is; that fallback is (silently) used also when the range has been given, but it's unknown.

Ticket History (3/8 Histories)

2022-05-29 11:03 Updated by: cazfi

• New Ticket "Ruleset sanity silently ignores unknown range" created

2022-07-19 16:40 Updated by: cazfi

• Milestone Update from (None) to 3.0.3 (closed)

2022-07-29 05:49 Updated by: cazfi

• Milestone Update from 3.0.3 (closed) to 3.0.4 (closed)

2022-08-05 12:00 Updated by: cazfi

• File 0033-Do-not-silently-ignore-invalid-range.patch (File ID: 10007) is attached

2022-08-05 12:01 Updated by: cazfi

• Owner Update from (None) to cazfi
• Resolution Update from None to Accepted

Comment

Requires that #45262 is fixed first, so that supplied rulesets won't start failing added check.

2022-08-10 10:27 Updated by: cazfi

• Resolution Update from Accepted to None

Comment

This is a bit harsh for existing S3_0 rulesets with the hard error. Should just give a warning there.

Often falling back to the default range even results in the wanted result.

2022-08-13 18:58 Updated by: cazfi

• File 0004-Do-not-silently-ignore-invalid-range.patch (File ID: 10068) is attached

2022-08-17 00:44 Updated by: cazfi

• Status Update from Open to Closed
• Resolution Update from None to Fixed