-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[BUG] Native Plugin Installation request for .asc and OpenSearch repo has the wrong Public Key #996
Comments
Answering questions in order:
Given that I see these as next steps:
|
|
The key from 05a6fde was generated back on April 9th for the public release build to pass. This was communicated back then when the pgp key was created and registered in the MIT keystore and was supposed to be the key used for signing the artifacts. Seems that was forgotten somewhere between April 9th and whenever https://opensearch.org/verify-signatures.html was generated so a different key was created. We can open a PR to use the new key but it would probably be a good idea to revoke the one that was initially created. /cc @camerski |
I've got all the info for the original key if you want to use that one instead of going through the process of revoking the original one. |
Sure, lets sync up on this one. Thanks. |
What are we doing about this? |
@peterzhuamazon/@camerski : has this issue been resolved? If not, could you move this issue to the right project? |
Hi @nknize can we have a talk on this? Thanks. |
Apparently it is only doing this for official plugins: Line 599 in 4906a3c
The plugins.txt is generated and save somewhere so all the native plugins are going through the verification: OpenSearch/server/build.gradle Line 210 in 7d18eaf
We need to discuss more on how to properly resolve this issue. |
Here's the original key registered with pgp.mit.edu that matches the public_key.asc file in PR #512. What do you want to do? Use it, or revoke it in favor of the other one (4096R/67F3A6AA) that was created? |
As we discussed today, the preferred solution for OpenSearch 1.1.0 and beyond is to change the signature check to use the user's normal PGP keyring so they can trust whichever public keys they choose, and add an option to the plugin installer to skip signature verification. For existing users we are discussing a couple of options for how to get them unblocked until 1.1.0 is ready. The options are:
Any other options? Thoughts? |
@camerski
Where was that discussed? was it in a thread in the forums? Was it in an internal AWS meeting perhaps?
a) please discuss in the open, as this is an open-source project that is supposedly "community driven" and "community-owned". |
@bbarani @peterzhuamazon Hey Peter, I've assigned this to you, but if you're the wrong person, please feel free to assign. Can you answer @AmiStrn's question? Thanks! |
Hi @CEHENKLE,
Thanks. |
Looking into this and will update labels shortly. |
This is still happening in tarball |
Using same reproduce steps? |
Sorry for the lack of description, this is the setup script I'm using:
It fails to install plugins with the same 403 error
Here is a DockerFile that fully reproduces the issue
|
You are installing 1.0.0 version of plugin on 1.1.0 which have different sig.
|
You can just |
Thanks, @peterzhuamazon that fixed the error. |
Describe the bug
Two issues:
opensearch-plugin
request to use.asc
file for validation instead of.sig
file, which we included in the signing and release process.05a6fde
The correct public key is here:
https://opensearch.org/verify-signatures.html
https://artifacts.opensearch.org/publickeys/opensearch.pgp
To Reproduce
See Above
Expected behavior
Install success
Plugins
analysis-icu
analysis-kuromoji
analysis-nori
analysis-phonetic
analysis-smartcn
analysis-stempel
analysis-ukrainian
discovery-azure-classic
discovery-ec2
discovery-gce
ingest-attachment
mapper-annotated-text
mapper-murmur3
mapper-size
repository-azure
repository-gcs
repository-hdfs
repository-s3
store-smb
transport-nio
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: