Simplify repo key handling #1233
Merged
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
sblaisot
force-pushed
the
new_repo_key_simplified
branch
from
bca6b44
to
f6d9103
Compare
pyrodie18
requested changes
May 24, 2024
This revert something that has been done after the last version has been published and is not something notable for users. Are you sure it needs a changelog fragment? |
pyrodie18
approved these changes
May 24, 2024
|
Fair |
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.
SUMMARY
Zabbix LLC finally published their new repo signing key in the same file than previous keys.
It is now time to revert extra complexity in repo key management added to accommodate new Ubuntu 24.04 repo being signed with a different key stored at a different location.
ISSUE TYPE
ADDITIONAL INFORMATION
Zabbix debian repository for Ubuntu 24.04 is signed with a brand new GPG key named
Zabbix LLC (Apr 2024)First they have forgotten to publish the key, then they have published it in a separate file than other previous keys.
This new key finally landed into the usual key file published alongside other older keys.
for more information, see https://support.zabbix.com/browse/ZBX-24443