-
Notifications
You must be signed in to change notification settings - Fork 53
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
W: GPG error: https://apt.corretto.aws stable InRelease: The following signatures were invalid: EXPKEYSIG #205
Comments
W: GPG error: https://apt.corretto.aws/ stable InRelease: The following signatures were invalid: EXPKEYSIG A122542AB04F24E3 Amazon Services LLC (Amazon Corretto release) corretto-team@amazon.com |
We observe a similar issue when running
Running |
Same issue for us while
|
We did Running command curl -fsSL https://apt.corretto.aws/corretto.key > /etc/apt/trusted.gpg.d/corretto.asc and echo Force cache invalidation prior to running apt-get update nothing working so far still seeing issue. |
Thank you for taking the time to help improve OpenJDK and Corretto.
If your request concerns a security vulnerability then please report it by email to aws-security@amazon.com instead of here. (You can find more information regarding security issues at https://aws.amazon.com/security/vulnerability-reporting/.)
Otherwise, if your issue concerns OpenJDK and is not specific to Corretto we ask that you raise it to the OpenJDK community. Depending on your contributor status for OpenJDK, please use the JDK bug system or the appropriate mailing list for the given problem area or update project.
If your issue is specific to Corretto, then you are in the right place. Please proceed with the following.
Describe the bug
We are seeing an issue while building our application on JDK 17
To Reproduce
Try to build an image with CorrettoJDK 17
Expected behavior
Should build successfully with out any issues and worked couple of days ago
Screenshots
If applicable, add screenshots to help explain your problem.
Platform information
Additional context
Add any other context about the problem here.
For VM crashes, please attach the error report file. By default the file name is
hs_err_pidpid.log
, where pid is the process ID of the process.The text was updated successfully, but these errors were encountered: