-
-
Notifications
You must be signed in to change notification settings - Fork 249
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
provide (gpg ?) signed releases #1275
Comments
I will have a look into this. |
Flag for TSC discussion too. |
@andrew-m-leonard Do you still plan to work on it? Would be really useful. |
@aahlenst not at the moment, so i've un-assigned myself thanks |
Why this is important (apart from the immediate security benefits): It allows mirroring our binaries and consuming them from 3rd party servers. This is also required as part of our move to Eclipse. The challenge here is where to sign and how. Having key material on the build machines is undesirable. Signing on the Jenkins master might be doable, but there only seems to be a plug-in for Maven. Using an Eclipse signing service would probably be best, but those are only accessible from selected machines controlled by the Eclipse Foundation. |
Related: require sigs in API: adoptium/api.adoptium.net#138 |
This is now progressing with an intention to have something usable for the July releases:
|
IBM releases are already signed: https://github.com/ibmruntimes/semeru17-binaries/releases/tag/jdk-17.0.3%2B7_openj9-0.32.0. |
Done and blog post is available at https://blog.adoptium.net/2022/07/gpg-signed-releases/ |
Please provided code-signed releases. (checksums are good but not enough)
Currently only the following releases are signed:
However, all .zip and .tar.gz releases which are provided via https://adoptopenjdk.net only have a checksum next to them, but no (gpg ?) signature is provided.
Or do I miss anything?
So currently we can check for integrity but not for authenticity.
Please provided signed releases on https://adoptopenjdk.net
Thank you!
The text was updated successfully, but these errors were encountered: