module
Noir::CLI::RulesCommand
Overview
noir rules <list|update|path>
Managed resource: the passive-scan rules repository (cloned from owasp-noir/noir-passive-rules into ~/.config/noir/passive_rules/).
Defined in:
cli/commands/rules.crConstant Summary
-
ACTIONS =
["list", "update", "path"] of ::String
Class Method Summary
-
.effective_rules_path : String
What
noir scan -Pactually reads rules from: the user-managed path when populated, otherwise the image-baked bundle at /opt/noir/passive_rules. - .list_rules(io : IO = STDOUT)
- .parse_argv(argv : Array(String)) : Parsed
- .print_help(io : IO = STDOUT)
-
.rules_path : String
The writable, user-managed rules directory: where
noir rules updateclones/pulls. - .run(argv : Array(String))
- .update_rules(debug : Bool = false, verbose : Bool = false)
Class Method Detail
What noir scan -P actually reads rules from: the user-managed path when
populated, otherwise the image-baked bundle at /opt/noir/passive_rules.
list/path report this so they never claim "no rules" on a Docker
install where passive scanning is fully working off the bundled ruleset.
The writable, user-managed rules directory: where noir rules update
clones/pulls. Kept distinct from .effective_rules_path (which may resolve
to the read-only image-baked bundle) so update always targets a path it
can actually write to.