reset signing key every month to detect revoked keys #241
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
robstoll
changed the title
with on pull I mean, not really every month but as soon as someone uses gt pull and the last check is more than a month ago. This is our mechanism to detect revoked keys, one can disable it by setting the lastCheck sometime in the future
robstoll
force-pushed
the
feature/check-signing-key
branch
from
5bd70d9 to
0120138
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
with on pull I mean, not really every month but as soon as someone uses gt pull and the last check is more than a month ago.
This is our mechanism to detect revoked keys, one can disable it by setting the lastCheck sometime in the future
I confirm that I have read the Contributor Agreement v1.1, agree to be bound on them and confirm that my contribution is compliant.