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

Use RSA/DSA/EC instead of PGP signatures for official plugins #41263

Closed
jkakavas opened this issue Apr 16, 2019 · 2 comments · Fixed by #44224
Closed

Use RSA/DSA/EC instead of PGP signatures for official plugins #41263

jkakavas opened this issue Apr 16, 2019 · 2 comments · Fixed by #44224
Labels
:Core/Infra/Plugins Plugin API and infrastructure >enhancement :Security/Security Security issues without another label

Comments

@jkakavas
Copy link
Member

jkakavas commented Apr 16, 2019

We validate the official plugins integrity and authenticity using BouncyCastle's PGP implementation. We could stop using PGP and rather depend on something simpler like RSA/DSA/ECDSA signatures for the plugin hashes . This would allow us to

  • Remove the dependency to BouncyCastle Security Provider for plugins-cli
  • Enable the plugin installer to work in a FIPS 140-2 approved only environment
@jkakavas jkakavas added >enhancement :Core/Infra/Plugins Plugin API and infrastructure :Security/Security Security issues without another label labels Apr 16, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-security

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Core/Infra/Plugins Plugin API and infrastructure >enhancement :Security/Security Security issues without another label
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants