Skip to content

feat: push signing keys to remote #3969

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

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

feat: push signing keys to remote #3969

wants to merge 1 commit into from

Conversation

sweatybridge
Copy link
Contributor

@sweatybridge sweatybridge commented Aug 1, 2025

What kind of change does this PR introduce?

feature

What is the new behavior?

Support updating signing keys with config push.

Additional context

TODO:

  • handle multiple standby keys

@sweatybridge sweatybridge requested a review from a team as a code owner August 1, 2025 17:29
@coveralls
Copy link

Pull Request Test Coverage Report for Build 16681317174

Details

  • 11 of 13 (84.62%) changed or added relevant lines in 1 file are covered.
  • 5 unchanged lines in 1 file lost coverage.
  • Overall coverage decreased (-0.03%) to 55.244%

Changes Missing Coverage Covered Lines Changed/Added Lines %
internal/gen/signingkeys/signingkeys.go 11 13 84.62%
Files with Coverage Reduction New Missed Lines %
internal/gen/keys/keys.go 5 12.9%
Totals Coverage Status
Change from base Build 16677900504: -0.03%
Covered Lines: 6184
Relevant Lines: 11194

💛 - Coveralls

@hf
Copy link
Contributor

hf commented Aug 4, 2025

Pushing a signing key is OK but it should come with a huge warning that the security of the key relies on the security of the device and person making the push.

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.

3 participants