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.

Sign up for GitHub

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

Jump to bottom

Investigate dealing with signed JARs #9

Open
benjholla opened this issue Jan 19, 2017 · 1 comment
Open

Investigate dealing with signed JARs #9

benjholla opened this issue Jan 19, 2017 · 1 comment
Labels
enhancement

Comments

@benjholla
Copy link
Member

So far Oracle/OpenJDK haven't been signing rt.jar, but if they did or if the user was editing a signed JAR then it's probably best to unsign the JAR and then let the user decide how to resign it with a newly generated key or a store key.
@benjholla benjholla mentioned this issue Apr 28, 2017
Closed
@benjholla
Copy link
Member Author

benjholla commented Apr 28, 2017 •
edited

Jars are automatically unsigned as of c1032b3 if they have changed since they would otherwise be identified as corrupted jars and fail to execute. A feature to resign and seal with a custom key store would be nice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@benjholla