8000 exit codes for command line tool · Issue #25 · badkeys/badkeys · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
exit codes for command line tool #25
Open
@hannob

Description

@hannob

We should have some strategy for exit codes for the commandline tool, currently badkeys doesn't set any.

It is a bit nontrivial, as we can scan multiple keys, and there can both be non-cryptographic warnings and vulnerabiltiy findings.

I am thinking about the following:

  • Return 0 if only "good" keys without vulnerabilities have been scanned.
  • Return 1 if any vulnerability has been found
  • Return 2 if any other problem happened
  • Return 3 if 1 and 2 would apply

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0