I am trying to run a .jnlp file using javaws. It produces this error:
Caused by: net.sourceforge.jnlp.LaunchException: Fatal: Application Error: The JNLP application is not fully signed by a single cert. The JNLP application has its components individually signed, however there must be a common signer to all entries.
It seems that the local java VM imposes these security restrictions. Now I am sure that the source of this .jnlp file is safe, and I really want to run it. To make it worse, downloading and opening the same file in Windows does work. No idea why that is?
How can I tell javaws to ignore this issue?
javaws -version: icedtea-web 1.6.2 (1.6.2-3.1)
debian stretch, kernel Linux 4.9.0-8-amd64
Edit: This post is considered a dupe of Running unsigned javaws code
However all possible solutions there do not work for me:
Did not work. Also, the statement that ~/.config/icedtea.web is an alias of .java/deployment is not true. The file does not exist at all in ~/.config/icedtea.web. At least not on my system. I linked the deployment.prpoerties to ~/.config/icedtea.web. To no avail.
I created a link so that ~/.config/icedtea.web points to .java/deployment/. Did not work either.
Then, it was recommended to comment out disabledAlgorithms in
I have multiple java.security files on my system, including in /etc and /usr. I commented out this line in all java.security files present on my system.
So maybe the post is a dupe of a similar problem, apparently it is something different as the proposed solutions do not solve the problem.
What information more can I provide to get closer to the cause? And why does it work in Windows right away without altering any security setting?