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

Please sign releases #1

Open
ben-willow opened this issue Apr 10, 2015 · 6 comments
Open

Please sign releases #1

ben-willow opened this issue Apr 10, 2015 · 6 comments

Comments

@ben-willow
Copy link

Please sign each release, so we can know provenance of future releases, and help protect against malicious updates.

@paulvi
Copy link

paulvi commented Sep 1, 2015

@ben-willow
Can you point to any case of malicious updates ?

@bekopharm
Copy link

It's common sense to install only signed packages. I may even be company policy and would increase acceptance. Don't wait for a malicious update to happen. Prevent it in the first place.

@paulvi
Copy link

paulvi commented Sep 22, 2015

For non Eclipse foundation plugins, I know only @jeeeyul Lee signing.

And that only creates additional questions asked to user
(while for Eclipse signed binaries there's no question asked)

@ncjones
Copy link
Owner

ncjones commented Sep 22, 2015

I agree this is common sense but I am unsure how to implement it. I've read through https://wiki.eclipse.org/JAR_Signing but this does not provide any advice for 3rd-party plugin authors. Nor did I find any advice when quickly searching through "Mastering Eclipse Plug-in Development" and "Eclipse Plug-ins, Third Edition". Any advice on how this should work?

@paulvi
Copy link

paulvi commented Sep 23, 2015

@ncjones Nathan, you can ask @jeeeyul

but I would suggest not to spend time on this

@cniweb
Copy link

cniweb commented Feb 16, 2017

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants