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

Question: Signed-Tags vs. Signed-Releases #845

Closed
azeemshaikh38 opened this issue Aug 12, 2021 · 3 comments · Fixed by #851
Closed

Question: Signed-Tags vs. Signed-Releases #845

azeemshaikh38 opened this issue Aug 12, 2021 · 3 comments · Fixed by #851
Assignees
Labels
kind/bug Something isn't working

Comments

@azeemshaikh38
Copy link
Contributor

I was wondering what the difference between our Signed-Tags and Signed-Releases check is. According to our README Signed-Tags tests if - the project cryptographically signs release tags?. 2 questions then:

  1. Our current implementation tests if all tags are signed and not just release tags. Is that a mistake?
  2. If we are concerned only with release tags, should we consider merging Signed-Tags and Signed-Releases checks into one?

@inferno-chromium @oliverchang @laurentsimon @naveensrinivasan thoughts?

@azeemshaikh38 azeemshaikh38 added the kind/bug Something isn't working label Aug 12, 2021
@naveensrinivasan
Copy link
Member

Signed Tags are Git Tags that are supposed to be signed. Not every tag would end up in releases.

Signed releases are when the releases are cryptographically signed.

I was wondering what the difference between our Signed-Tags and Signed-Releases check is. According to our README Signed-Tags tests if - the project cryptographically signs release tags?. 2 questions then:

  1. Our current implementation tests if all tags are signed and not just release tags. Is that a mistake?

It is not. Not all git tags end up with releases, it is based on the project's release criteria.

  1. Signed tags are for all git tags
  2. Signed releases for not for tags but for the actual release.

This is incorrect Does the project cryptographically sign release tags? for Signed-Tags and needs to be fixed. The details have the correct description https://github.com/ossf/scorecard/blob/main/docs/checks.md#signed-tags

  1. If we are concerned only with release tags, should we consider merging Signed-Tags and Signed-Releases checks into one?

@inferno-chromium @oliverchang @laurentsimon @naveensrinivasan thoughts?

@azeemshaikh38
Copy link
Contributor Author

Makes sense. Although how is testing all Git tags useful to users? IIUC, if these Git tags aren't used in releases, users would never see/use these tags?

@inferno-chromium
Copy link
Contributor

We probably don't even need signed tags check. i think we should keep just a signed releases check. @dlorenc for additional thoughts ?

@azeemshaikh38 azeemshaikh38 linked a pull request Aug 12, 2021 that will close this issue
2 tasks
@azeemshaikh38 azeemshaikh38 self-assigned this Aug 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants