Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add info about which signing keys will be used for published artifacts. #767

Open
yogurtearl opened this issue Sep 4, 2023 · 1 comment

Comments

@yogurtearl
Copy link

Add info about which signing keys will be used for published artifacts.

Looks like the signing key changed for the 20230618 release.

20230618 appears to be signed with this key: https://keyserver.ubuntu.com/pks/lookup?search=fb35c8d02b4724dada23de0afd116c1969fccff3&fingerprint=on&op=index

For security purposes, it would be great if you were able to publish details (in the project docs) about the gpg public keys that are "valid" for use when verifying signing artifacts uploaded to maven central.

This allows for "out of band" verification of the expected signing key.

Some examples of other libs publishing their signing keys:

https://square.github.io/okhttp/security/security/#verifying-artifacts

https://github.com/eclipse/jetty.project/blob/jetty-10.0.x/KEYS.txt
https://downloads.apache.org/commons/KEYS
https://downloads.apache.org/logging/KEYS

@mathjeff
Copy link

Thanks - I was wondering about this too, and the key I noticed for json-20231013.pom seems to match the one you mention in this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants