packer plugin signing key
-
my apologies if i just missed this or if I'm just blind today, but I cannot for the life of me find the signing key (0DD2E92A7A0F682BC29F87073084D82948625D89) for the packer plugin.
i checked the xcp-ng official signing key but it has an id of 34AC2EB68248FED6D076838ACD75783A3FD3AC9E.
can somebody please point me in the right direction?
TIA

-
You're not blind, and your fingerprint is right. I pulled
packer-plugin-xenserver_v0.11.4_SHA256SUMS.sigoff the GitHub release and rangpg --list-packetson it, and it reportsissuer fpr v4 0DD2E92A7A0F682BC29F87073084D82948625D89, which is exactly what you pasted.It doesn't match the XCP-ng key because it isn't ours.

The plugin our docs point at is
ddelnano/packer-plugin-xenserver, maintained outside Vates, so it's signed with the maintainer's key while34AC2EB6...only signs XCP-ng RPMs.I couldn't find that key published anywhere either. It's not on keys.openpgp.org or keyserver.ubuntu.com, it isn't in the repo, and it isn't among the 11 keys at
github.com/ddelnano.gpg.That looks like something worth raising on the plugin's own issue tracker, and you'd file it better than I would since you're the one trying to verify a download. I'd also say our IaC docs could stand to mention the plugin isn't ours, which is what sent you looking at the wrong key in the first place.
-
thanks @poddingue

I've opened: https://github.com/vatesfr/packer-plugin-xenserver/issues/212
-
@enkaskal I need to correct my reply above, I got two things wrong. The plugin is ours after all:
ddelnano/packer-plugin-xenserveris the repo's old address, it moved tovatesfr/packer-plugin-xenserver(where you filed #212), and GitHub just redirects the old link, which I read on our IaC docs page and jumped to the wrong conclusion.
The key isn't missing either, I just didn't look in the right place: it's the signing key the Terraform Registry lists for vatesfr/xenorchestra, so you can fetch it from there.
curl -s https://registry.terraform.io/v1/providers/vatesfr/xenorchestra/0.41.2/download/linux/amd64 \ | jq -r '.signing_keys.gpg_public_keys[0].ascii_armor' > xenorchestra-signing.asc gpg --import xenorchestra-signing.asc gpg --verify packer-plugin-xenserver_v0.12.0_SHA256SUMS.sig packer-plugin-xenserver_v0.12.0_SHA256SUMSOn my machine the last command reports a good signature from
0DD2E92A7A0F682BC29F87073084D82948625D89, still a key in Dom Delnano's name from before the move. I'm honestly not sure how much trust that gives you beyond "the registry vouches for the same key", so I'd leave that part to the folks on #212 who know the release side better than me. Sorry for the detour.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login