rbehjati
rbehjati
> I think this is probably obsolete, right? I think so. Closing it.
In the future, this can be extended to publish the signatures into Rekor. We would also want to know if it is possible to have a single GitHub action with...
The following are some of the information that the client might want to verify. The actual verification depends on the Client. - hash of web assembly - metrics configuration (differential...
Possibly a duplicate of #2535. See also #2248.
## What to do with additional_info? We have to clarify what `additional_info` is for. Is this additional info that the server sends to the client to verify, or does it...
I think at some point we have been using https://github.com/project-oak/oak/blob/00c87846b6988f89f76d9f35e2633b60e08b0f64/scripts/run_tests_coverage. But now the command is incorrect, and I hope it is not being used anywhere. This is where we previously...
I found this earlier PR: https://github.com/project-oak/oak/commit/56ee7fa6b625b59244eff9b45467af5ec662613a This issue gives more info: https://github.com/project-oak/oak/issues/1187 Interestingly, we still have https://github.com/project-oak/oak/blob/main/.codecov.yml in the code base. I don't think we'd want to use codecov anymore...
I think the correct functionality is to fail when no configuration info is provided. So I think the Rust client must be updated.
Possibly a duplicate of #2354.
> @rbehjati how would you communicate the `payloadType` in your CLI invocation? We use `rekor-cli upload` with `--type rekord`. If you are referring to the payload type in the envelope,...