Where is the Github asc file for their pgp signing key? #130439
Replies: 4 comments
-
GitHub does not generally provide an .asc file for their keys as they focus on verifying the authenticity of commits and tags. This is usually done by the source maintainer. The best way to verify the authenticity of a release is to verify the tag associated with the release, then verify the commit associated with the tag:
git show --show-signature 6ce44a9 Then compare the info with the github (by clicking on the commit hash of the first image: |
Beta Was this translation helpful? Give feedback.
-
I'm trying to verify a download from a release. Github really does not have their key in asc format anywhere? |
Beta Was this translation helpful? Give feedback.
-
I dont think so. Sorry. Generally the projects maintainers are the ones who provides the GPG signature for their files. You can take a look in the GitHub's docs for code security and commit signature verification. |
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
The releases I'm downloading from Github are signed with key B5690EEEBB952194. That's Github's signing key. However, I cannot find the asc file for confirming the executable I have downloaded is actually from Github's servers, and not some man in the middle attacking my infrastructure.
Obviously, it would be preferable for the developer to sign their own releases with their own key. However, if I can find the Github asc file at least I can confirm whether the file is signed by Github's key or not.
Does anyone know where that file is so I can confirm the release contents are signed?
Beta Was this translation helpful? Give feedback.
All reactions