Add more details to the output about csaf_distribution HOT 9 CLOSED

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

from csaf_distribution.

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

from csaf_distribution.

Moved the client certificate part to #46.

from csaf_distribution.

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?

from csaf_distribution.

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?

from csaf_distribution.

Let's discuss this on Friday.

from csaf_distribution.

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.

from csaf_distribution.

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
        ]
    }
  ]
}

from csaf_distribution.

I think, PR #238 has solved this.

from csaf_distribution.