class OutputBuilderPassiveScan
- OutputBuilderPassiveScan
- OutputBuilder
- Reference
- Object
Defined in:
output_builder/passive_scan.crInstance Method Summary
-
#print(passive_results : Array(PassiveScanResult))
Findings go out through
ob_puts, like every other builder's report content, rather than straight to the logger. - #severity_color(severity : String) : String
Instance methods inherited from class OutputBuilder
bake_endpoint(url : String, params : Array(Param))
bake_endpoint,
io : IO
io,
io=(io : IO)
io=,
logger : NoirLogger
logger,
ob_puts(message)
ob_puts,
output_file : String
output_file,
print
print
Constructor methods inherited from class OutputBuilder
new(options : Hash(String, YAML::Any))
new
Instance Method Detail
def print(passive_results : Array(PassiveScanResult))
#
Findings go out through ob_puts, like every other builder's report
content, rather than straight to the logger. Three things follow from
that, and none of them held before:
-ofinally receives the findings.noir scan . -P -o report.txtwrote the endpoint list to the file and left the secrets on stdout only, so the saved report was missing the part-Pwas run for.- The file copy is plain text, and so is a redirected stdout. The
is_colorthis used to be handed came fromNoirRunner, which reads thecoloroption with no terminal check because that same flag also colors stderr progress logs;@is_colorhere is the TTY-aware one, so-P > findings.txtno longer gets ANSI codes. - A closed downstream pipe (
| head) stops the stdout writes but lets the-ofile finish, instead ofexit(0)-ing mid-report.