Jar's CodeSigner null on Java 10, non-null on Java 8
Alan Bateman
Alan.Bateman at oracle.com
Sun Oct 7 07:49:26 UTC 2018
On 06/10/2018 06:21, Scott Palmer wrote:
> As is too often the case I discovered the difference while trying to
> isolate a test case. With Java 10 I had extra JVM args to deal with
> module path and that appeared to cause the problem.
There is very limited support for signing of modules and signed modular
JARs. JDK-8194930 [1] tracks the issue of the protection domain not
including the signing info but there are other issues, mostly at
link-time where jlink will report an error if you attempt to creating a
run-time image containing a signed module.
-Alan
[1] https://bugs.openjdk.java.net/browse/JDK-8194930
More information about the security-dev
mailing list