-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
csaf_checker fails in jsonPath without referencing the input data it fails on #24
Comments
Hi @tolim The failure comes from a call to csaf_distribution/cmd/csaf_checker/processor.go Lines 177 to 179 in 2a69c13
So I guess that some required attribute is missing from the We'll take this as a hint to add more diagnostic messages. |
The decoding of the metadata fails earlier, but this error is wrongly rated as none essential and is only written to the report. I'm going to fix this. |
…tion pointless. Fixes issue #24. TODO: Improve handling of checks that are not run due to the stop. They currently report success which is not correct.
PR #26 introduces a mechanism to stop a running domain check and still dump out the report. This needs some work because the parts of the check which do not run due to the stop are currently marked as successful. This is not correct. |
Second part of the Fix of issue #24.
I was stumbling upon csaf_distribution/cmd/csaf_checker/processor.go Lines 708 to 712 in c57de75
but I might be on the wrong track: The
More than one may exist, however to be valid at least one MUST exist... Even though the .well-known path is preferred it is not the only option here. |
I suggest we make the location of the As far as I know, the first issue here is improved: we get a diagnostic message now with current main. |
Sounds good to me. |
The situation has improved. A call like
now contains the following in the output: "domains": [
{
"name": "example.org",
[..]
"description": "provider-metadata.json",
"messages": [
"No provider-metadata.json found.",
"STOPPING here - cannot perform other checks."
So we believe this issue to be resolved. |
When trying to check a domain with the csaf_checker, I get the following error message:
Why does the command fail?
Thanks in advance!
Tobi
The text was updated successfully, but these errors were encountered: