Skip to content

Fix Jitsi Prosody repo apt key handling - #244

Open
PeterDaveHello wants to merge 1 commit into
digitalocean:masterfrom
PeterDaveHello:fix/prosody-keyring
Open

Fix Jitsi Prosody repo apt key handling#244
PeterDaveHello wants to merge 1 commit into
digitalocean:masterfrom
PeterDaveHello:fix/prosody-keyring

Conversation

@PeterDaveHello

@PeterDaveHello PeterDaveHello commented Nov 7, 2025

Copy link
Copy Markdown

Apt 2.4+ rejects signed-by entries that reference raw ASCII keys, triggering NO_PUBKEY F7A37EB33D0B25D7 for the Prosody repo.

Pipe the downloaded key through gpg --dearmor so droplet builds keep a binary keyring apt accepts, and add --batch --yes so reruns can overwrite the file without gpg errors.

This pull request updates the way the Prosody package signing key is added in both the jitsi-22-04 and jitsi-24-04 setup scripts. The new approach uses gpg --dearmor for improved security and compatibility.

GitHub Copilot Summary:

Improved repository key handling:

  • Replaced the direct download of the Prosody signing key with a pipeline that fetches the key and converts it to a GPG keyring format using gpg --dearmor in both jitsi-22-04/scripts/01-packages.sh and jitsi-24-04/scripts/01-packages.sh. This enhances security and aligns with best practices for managing APT repository keys.

Apt 2.4+ rejects signed-by entries that reference raw ASCII keys,
triggering NO_PUBKEY F7A37EB33D0B25D7 for the Prosody repo. Pipe the
downloaded key through gpg --dearmor so droplet builds keep a binary
keyring apt accepts, and add --batch --yes so reruns can overwrite the
file without gpg errors.
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.

1 participant