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

Allow developers to verify there jar file with a sign key #1215

Open
TheMeinerLP opened this issue Apr 30, 2023 · 0 comments
Open

Allow developers to verify there jar file with a sign key #1215

TheMeinerLP opened this issue Apr 30, 2023 · 0 comments
Labels
1. feature New feature or request 2. backend This issue/pr relates to an issue/change on the backend 2. frontend This issue/pr relates to an issue/change on the frontend

Comments

@TheMeinerLP
Copy link

TheMeinerLP commented Apr 30, 2023

Is your feature request related to a problem?

Not direct related to a problem its just a nice to have feature.

Describe the solution you'd like.

  1. Have on the profile a option to add gpg keys of a use/organization.
  2. Sign jar files over the hangar publish plugin
  3. Get a badge/status on the plugin to see the developer use gpg key to sign there plugin
  4. A rest api endpoint for other developers to get the key to test the plugin for a source of truth.

Describe alternatives you've considered.

Don't implemented or just the option to add and get the key from the rest api and ui.

Other

image
Mockup was i made with simple html editing
image
I added also a small verified icon on the end of the plugin name.
Also a example of orga ui
image
image
Here a example for the whole plugin list

@kennytv kennytv added 1. feature New feature or request 2. frontend This issue/pr relates to an issue/change on the frontend 2. backend This issue/pr relates to an issue/change on the backend labels May 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. feature New feature or request 2. backend This issue/pr relates to an issue/change on the backend 2. frontend This issue/pr relates to an issue/change on the frontend
Projects
Status: New
Development

No branches or pull requests

2 participants