-
Bug
-
Resolution: Fixed
-
Blocker
-
All platforms where you can use at least Java web start to get a slave node connected, and Java 7 update 45 installed.
Since I have installed Java 7 update 45 on our test slaves I get the following security warning:
Running applications by UNKNOWN publishers will be blocked in a future release because it is potentially unsafe and a security risk.
This application will be blocked in a future Java security update because the JAR file manifest does not contain the Permissions attribute. Please contact the Publisher for more information.
It looks like that the .jar file(s) do not contain a permissions attribute, which would let slaves connect to the master in the future. In our case we connect slaves via Java web start.
As of now it is not a hard-blocker and you can click through and accept. But I think that this should be fixed soon.
- is duplicated by
-
JENKINS-22374 JNLP slaves blocked by default using Java 7u45/51
- Resolved
- is related to
-
JENKINS-21570 Slave JNLP not signed by a CA causes issues with Java 7.51
- Resolved