28E72909F1717FE9607754F8A7BEB2621678D37D key not specified in builder keys and 24.0 release signed with it #26566

1. 
   scgbckbone commented at 3:37 pm on November 24, 2022: none

   I would expect each key that signs new release to be included in contrib/builder-keys/keys.txt - am I wrong? 24.0 is signed with 28E72909F1717FE9607754F8A7BEB2621678D37D vertion@protonmail.com but this key is not included in keys.txt.

   If above is not true, where does one find all the keys that sign new releases ?

2. scgbckbone added the label Bug on Nov 24, 2022
3. maflcko removed the label Bug on Nov 24, 2022
4. maflcko added the label Questions and Help on Nov 24, 2022
5. 
   willcl-ark commented at 3:48 pm on November 24, 2022: contributor

   @scgbckbone anybody can sign new builds using the Guix build system. If you sign 3 or more releases then you can open a PR to have your key added to builder-keys/keys.txt.

   You can find “missing” keys on keyservers, e.g. openpgp or ubuntu.

6. 
   maflcko commented at 3:50 pm on November 24, 2022: member

   It is not required to find all keys. Only the keys of the people you (want to) trust.
7. 
   scgbckbone commented at 3:53 pm on November 24, 2022: none

   thanks for your answers!
8. scgbckbone closed this on Nov 24, 2022

   ---

9. maflcko referenced this in commit 296e882250 on Jan 5, 2023
10. bitcoin locked this on Nov 24, 2023

Contributors
scgbckbone willcl-ark maflcko

Labels
Questions and Help