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: Regression in signature verification for git tags #12797

Merged
merged 1 commit into from Apr 4, 2023

Conversation

jannfis
Copy link
Member

@jannfis jannfis commented Mar 10, 2023

Fixes #7377

There was a regression not covered by tests when we changed passing the resolved commit SHA (instead of the symbolic reference) to verification routines, which resulted in trying to run git verify-tag on a commit SHA a tag was pointing to, instead of running against the tag.

Note on DCO:

If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • Optional. My organization is added to USERS.md.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).

Signed-off-by: jannfis <jann@mistrust.net>
@codecov
Copy link

codecov bot commented Mar 10, 2023

Codecov Report

❗ No coverage uploaded for pull request base (master@558140f). Click here to learn what that means.
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff            @@
##             master   #12797   +/-   ##
=========================================
  Coverage          ?   47.77%           
=========================================
  Files             ?      246           
  Lines             ?    41986           
  Branches          ?        0           
=========================================
  Hits              ?    20058           
  Misses            ?    19929           
  Partials          ?     1999           
Impacted Files Coverage Δ
reposerver/repository/repository.go 60.51% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@crenshaw-dev
Copy link
Collaborator

/cherry-pick release-2.4

@crenshaw-dev
Copy link
Collaborator

/cherry-pick release-2.5

@crenshaw-dev
Copy link
Collaborator

/cherry-pick release-2.6

@jannfis
Copy link
Member Author

jannfis commented Apr 2, 2023

@crenshaw-dev bump :)

@crenshaw-dev
Copy link
Collaborator

crenshaw-dev commented Apr 4, 2023

/cherry-pick release-2.7

@crenshaw-dev crenshaw-dev merged commit 7ee1ee3 into argoproj:master Apr 4, 2023
18 checks passed
gcp-cherry-pick-bot bot pushed a commit that referenced this pull request Apr 4, 2023
Signed-off-by: jannfis <jann@mistrust.net>
gcp-cherry-pick-bot bot pushed a commit that referenced this pull request Apr 4, 2023
Signed-off-by: jannfis <jann@mistrust.net>
gcp-cherry-pick-bot bot pushed a commit that referenced this pull request Apr 4, 2023
Signed-off-by: jannfis <jann@mistrust.net>
gcp-cherry-pick-bot bot pushed a commit that referenced this pull request Apr 4, 2023
Signed-off-by: jannfis <jann@mistrust.net>
crenshaw-dev pushed a commit that referenced this pull request May 28, 2023
Signed-off-by: jannfis <jann@mistrust.net>
Co-authored-by: jannfis <jann@mistrust.net>
crenshaw-dev pushed a commit that referenced this pull request May 28, 2023
Signed-off-by: jannfis <jann@mistrust.net>
Co-authored-by: jannfis <jann@mistrust.net>
crenshaw-dev pushed a commit that referenced this pull request May 28, 2023
Signed-off-by: jannfis <jann@mistrust.net>
Co-authored-by: jannfis <jann@mistrust.net>
schakrad pushed a commit to schakrad/argo-cd that referenced this pull request Jul 24, 2023
… (argoproj#13113)

Signed-off-by: jannfis <jann@mistrust.net>
Co-authored-by: jannfis <jann@mistrust.net>
Signed-off-by: schakrad <58915923+schakrad@users.noreply.github.com>
yyzxw pushed a commit to yyzxw/argo-cd that referenced this pull request Aug 9, 2023
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.

ArgoCD complains about revision being unsigned when using a tag
2 participants