Update Debian/Ubuntu package signing key location to /etc/apt/keyrings for improved security #6298
Conversation
This file contains hidden or 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
…pt/keyrings Co-authored-by: jstirnaman <212227+jstirnaman@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Debian/Ubuntu package signing key location - update to /etc/apt/keyrings?
Update Debian/Ubuntu package signing key location to /etc/apt/keyrings for improved security
Aug 13, 2025
jstirnaman
reviewed
Aug 14, 2025
jstirnaman
approved these changes
Aug 19, 2025
Add exclusion patterns for StackExchange sites to both production and default link-checker configurations: - *.stackexchange.com - stackoverflow.com - *.stackoverflow.com These sites often block automated requests/bots, causing false positive link validation failures in CI environments.
Add exclusion pattern for hub.docker.com to both production and default link-checker configurations. Docker Hub often implements rate limiting and bot detection that causes false positive link validation failures in CI environments.
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.
Updates the APT package signing key storage location from
/etc/apt/trusted.gpg.d/to/etc/apt/keyrings/across all InfluxData installation documentation to follow modern security best practices.Background
The current documentation instructs users to store GPG keys in
/etc/apt/trusted.gpg.d/, which creates globally trusted keys for all repositories. This approach is less secure because these keys are trusted system-wide and cannot be restricted to specific repositories.The modern recommended approach uses
/etc/apt/keyrings/with thesigned-byoption in sources lists, providing better security isolation by allowing per-repository key assignment rather than global trust.Changes Made
Updated installation instructions in 5 documentation files:
content/telegraf/v1/install.md) - Both Ubuntu 20.04+ and legacy versionscontent/influxdb/v1/introduction/install.md) - Both installation methodscontent/influxdb/v2/install/_index.md) - Ubuntu/Debian sectioncontent/influxdb3/clustered/reference/cli/influxctl/_index.md)content/influxdb3/cloud-dedicated/reference/cli/influxctl/_index.md)Technical Details
The changes replace:
With:
This maintains full backward compatibility while improving security isolation. The
/etc/apt/keyrings/directory is supported in apt 2.4+ (Ubuntu 22.04+, Debian 12+), and the existingsigned-byconfiguration ensures proper per-repository key assignment.Fixes #6297.
Warning
Firewall rules blocked me from connecting to one or more addresses
I tried to connect to the following addresses, but was blocked by firewall rules:
download.cypress.ioIf you need me to access, download, or install something from one of these locations, you can either:
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.