There were few topics before:
Every 23.05 release contains the same note and promises that later release will have different key.
Could someone explain why the latest 23.05.5 has been signed with the wrong key?
There were few topics before:
Every 23.05 release contains the same note and promises that later release will have different key.
Could someone explain why the latest 23.05.5 has been signed with the wrong key?
That didn't mean version 24?
So, does anybody know whether or not we are going to have any 23.05 release with the correct keys? And why the wrong keys have been used for a long period?
This seems very much a question worth asking. Anybody able to answer this?
I asked the same thing on .3
No one is fixing the release workflow so it will continue to be wrong.
Here's the answer:
And documentation:
https://openwrt.org/docs/guide-developer/releases/provision-nitrokey3
@ynezz do you want any assistance with the artifact signing REST API service?
Thanks for pointing. At least I understand now what is the root of issue.
@ynezz, how can I help you to have correct keys used for the latest OpenWRT release?
Just for information.
ynezz on Nov 9, 2024
We've just finished switching all buildmasters to the new key, so from now on, everything should be signed with the Universal GPG signing key from Nitrokey 3A key.