Add more details to the output

[tschmidtb51]

From a user's perspective, it would be beneficial to have more details (or at least an option for it) in the output. It should include:

• Information from the publisher object
• role
• Path of the provider-metadata.json found as link
• whether the provider-metadata.json is valid
• Path of the security.txt tested/found
• whether ROLIE feeds exist, where and whether they are valid

[tschmidtb51]

One should also be able to provide a TLS client certificate to use for the TLP:AMBER and TLP:RED feeds.

[bernhardreiter]

Moved the client certificate part to #46.

[JanHoefelmeyer]

Talked to @bernhardreiter, tested version: 0.9.2-10-g006f088
Tested output.

Unclear what "role" means.
No information from the publisher object present.
For provider-metadata.json, only info provided was whether it was found.
For security.txt, no path was provided.
No ROLIE feed information was provided.

Then, tried out the verbose option:
Now additional information was written into the log above the standard output:
Location of security.txt and provider-metadata.json:
2022/06/14 12:38:01 [GET]: https://localhost/.well-known/security.txt
2022/06/14 12:38:01 [GET]: https://localhost/.well-known/csaf/provider-metadata.json

No information about the other points.
Should the information about these files (as well as the other still missing information) be moved into the standard output or stay within the verbose option?

[JanHoefelmeyer]

Opened a new issue #184 for the ROLIE feed part of the issue.

[bernhardreiter]

The output for check 9 related to the validity of the used provider-metadata.json and --verbose shows the URLs for all access attempts.

@tschmidtb51 Do you agree that this is enough for paths and validity for the provider-metadata.json?

[tschmidtb51]

Let's discuss this on Friday.

[bernhardreiter]

Wished for is to print the publisher and role object values from the provider-metadata.json that is used. (Acceptable would be to have this as diagnostic output on the command line behind --verbose. )

And give out the path of the provider-metadata.json that is used.

[tschmidtb51]

If it is integrated into the standard output, I suggest the following location in the json:

{
  "domains": [
    {    
      "name": "any.domain.name.example",
      "publisher": {
         // Publisher details here
       },
       "role": "csaf_provider",
       "requirements": [
          // Test results here
        ]
    }
  ]
}

[s-l-teichmann]

I think, PR #238 has solved this.