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

Security manager preventing EqualsVerifier to create dynamic subclass #163

Closed
sywor opened this issue Dec 15, 2016 · 5 comments
Closed

Security manager preventing EqualsVerifier to create dynamic subclass #163

sywor opened this issue Dec 15, 2016 · 5 comments
Labels

Comments

@sywor
Copy link

sywor commented Dec 15, 2016

The steps are pretty well described here.
If there is a abstract class in a signed jar that is extended in an other class the security manager throws an security exception when the equals verifier tries to create an dynamic subclass in the signed jar.

What error message or stack trace does EqualsVerifier give?

java.lang.SecurityException: class "...ExternalClass$$DynamicSubclass"'s signer information does not match signer information of other classes in the same package

Which version of EqualsVerifier are you using?

2.1.8

Please provide any additional information below.

I'm adding this issue here for bookkeeping. The issue could possibly be solved by using prefab values.

@jqno
Copy link
Owner

jqno commented Dec 15, 2016

As I've asked in the thread you link to, you have to help me out here. Can you please give me such a jar, or show me how to make one, so I can reproduce this issue?
I really want to fix this issue, but I have no experience with signed jars and work is keeping me pretty busy, so if you help me out I can fix it much sooner than if I have to figure everything out myself...

@sywor
Copy link
Author

sywor commented May 15, 2017

Its been a while and my colleague finally had some spare time over to throw together a small project to demonstrate the bug.
Link to project: https://github.com/sywor/EqualsVerifierBug
In the ExternalProject pom file it is important that you set the path the the .keystore file

@jqno
Copy link
Owner

jqno commented May 16, 2017

Thank you, and also please thank your colleague for taking the time to do this 😄.
I was able to reproduce the issue with this repo. I will investigate further, and I'll get back to you when I know more.

@jqno
Copy link
Owner

jqno commented May 19, 2017

I found a solution for this issue!
I have a couple of other things I want to do before I release, but they shouldn't take too much time. I'll let you know when it's released.

@jqno
Copy link
Owner

jqno commented May 24, 2017

I've just released version 2.3, which should fix this problem.

@jqno jqno closed this as completed May 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants