[llvm-dev] Keys used to sign releases

don hinton via llvm-dev llvm-dev at lists.llvm.org
Wed Aug 9 20:57:07 PDT 2017


I see that some, but not all, releases provide a local link to the key used
to generate the signature files, which makes it difficult for a script to
use them to verify the signatures.

Gcc solves this problem by including the following on their mirrors page (
https://gcc.gnu.org/mirrors.html):

The archives there will be signed by one of the following GnuPG keys:

   - 1024D/745C015A 1999-11-09 Gerald Pfeifer <gerald at pfeifer.com>
   Key fingerprint = B215 C163 3BCA 0477 615F 1B35 A5B3 A004 745C 015A
   - 1024D/B75C61B8 2003-04-10 Mark Mitchell <mark at codesourcery.com>
   Key fingerprint = B3C4 2148 A44E 6983 B3E4 CC07 93FA 9B1A B75C 61B8
   - 1024D/902C9419 2004-12-06 Gabriel Dos Reis <gdr at acm.org>
   Key fingerprint = 90AA 4704 69D3 965A 87A5 DCB4 94D0 3953 902C 9419
   - 1024D/F71EDF1C 2000-02-13 Joseph Samuel Myers <jsm at polyomino.org.uk>
   Key fingerprint = 80F9 8B2E 0DAB 6C82 81BD F541 A7C8 C3B2 F71E DF1C
   - 2048R/FC26A641 2005-09-13 Richard Guenther <richard.guenther at gmail.com>
   Key fingerprint = 7F74 F97C 1034 68EE 5D75 0B58 3AB0 0996 FC26 A641
   - 1024D/C3C45C06 2004-04-21 Jakub Jelinek <jakub at redhat.com>
   Key fingerprint = 33C2 35A3 4C46 AA3F FB29 3709 A328 C3A2 C3C4 5C06

Would it make sense to add something similar to our download page?

thanks...
don
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170809/d39d95d0/attachment.html>


More information about the llvm-dev mailing list