Skip to content
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

fix: remove signing certificate output #160

Merged
merged 5 commits into from
Jul 22, 2022

Conversation

asraa
Copy link
Contributor

@asraa asraa commented Jul 21, 2022

Signed-off-by: Asra Ali asraa@google.com

Fixes #156

Updates README.md with the new output.

Signed-off-by: Asra Ali <asraa@google.com>
Signed-off-by: Asra Ali <asraa@google.com>
Signed-off-by: Asra Ali <asraa@google.com>
@laurentsimon
Copy link
Contributor

laurentsimon commented Jul 22, 2022

lots of really interesting error messages in the log. One I had not seen before: Getting rekor entry error error searching rekor entries: [POST /api/v1/log/entries/retrieve][400] searchLogQueryBadRequest &{Code:400 Message:invalid public key: failure decoding PEM}, trying Redis search index to find entries by subject digest ... maybe that's one that'ex expected given the unit tests actually.

May be useful to separate the list of message by a comma. I created #161 to improve the logging we have and make it more structured / standard.

@asraa
Copy link
Contributor Author

asraa commented Jul 22, 2022

Oh, the error messages were from #159, not this PR.

error messages were added with a separated comma: https://github.com/asraa/slsa-verifier/blob/0c6f7c68bde9fd305579e11f86e40a79019e2451/pkg/rekor.go#L394

Maybe a newline? I"ll do that in the follow-up, not this PR

@asraa
Copy link
Contributor Author

asraa commented Jul 22, 2022

One I had not seen before: Getting rekor entry error error searching rekor entries: [POST /api/v1/log/entries/retrieve][400] searchLogQueryBadRequest &{Code:400 Message:invalid public key: failure decoding PEM}, trying Redis search index to find entries by subject digest ... maybe that's one that'ex expected given the unit tests actually.

I saw this one too, and I realize it's likely because there was no certificate PEM in the intoto envelope for the older builder tests. So rekor fails to decode the empty string PEM. Just added an error condition to prevent Rekor query if the cert is empty, so that'll be a clearer error message.

Signed-off-by: Asra Ali <asraa@google.com>
@laurentsimon
Copy link
Contributor

Ready to merge?

@asraa
Copy link
Contributor Author

asraa commented Jul 22, 2022

Yes!

@asraa asraa merged commit 8c4373c into slsa-framework:main Jul 22, 2022
laurentsimon pushed a commit to laurentsimon/slsa-verifier that referenced this pull request Aug 3, 2022
* remove signing certificate output

Signed-off-by: Asra Ali <asraa@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove the default JSON output
2 participants