Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-20204

Latest release of Java 7 blocks the connection to slaves due to no permissions attribute in the JAR file

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Blocker
    • Resolution: Fixed
    • Component/s: core
    • Environment:
      All platforms where you can use at least Java web start to get a slave node connected, and Java 7 update 45 installed.
    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Kohsuke Kawaguchi
            Path:
            changelog.html
            pom.xml
            http://jenkins-ci.org/commit/jenkins/11458c956e64673d99a9dc2c05cfd5f9533b4e1b
            Log:
            [JENKINS-20769 JENKINS-20204] integrated remoting 2.35 in the core.

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html pom.xml http://jenkins-ci.org/commit/jenkins/11458c956e64673d99a9dc2c05cfd5f9533b4e1b Log: [JENKINS-20769 JENKINS-20204] integrated remoting 2.35 in the core.
            Hide
            dogfood dogfood added a comment -

            Integrated in jenkins_main_trunk #3267
            [JENKINS-20769 JENKINS-20204] integrated remoting 2.35 in the core. (Revision 11458c956e64673d99a9dc2c05cfd5f9533b4e1b)

            Result = SUCCESS
            kohsuke : 11458c956e64673d99a9dc2c05cfd5f9533b4e1b
            Files :

            • pom.xml
            • changelog.html
            Show
            dogfood dogfood added a comment - Integrated in jenkins_main_trunk #3267 [JENKINS-20769 JENKINS-20204] integrated remoting 2.35 in the core. (Revision 11458c956e64673d99a9dc2c05cfd5f9533b4e1b) Result = SUCCESS kohsuke : 11458c956e64673d99a9dc2c05cfd5f9533b4e1b Files : pom.xml changelog.html
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Kohsuke Kawaguchi
            Path:
            pom.xml
            http://jenkins-ci.org/commit/jenkins/a89aa713b2ba5c325cd296d5733a565aa5cc63ec
            Log:
            [JENKINS-20769 JENKINS-20204] Integrating remoting 2.36

            Fixed a bug Jesse found in remoting

            (cherry picked from commit 75447b57b655e38fdb48f1e854a4b287071342cf)

            Conflicts:
            pom.xml

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Kohsuke Kawaguchi Path: pom.xml http://jenkins-ci.org/commit/jenkins/a89aa713b2ba5c325cd296d5733a565aa5cc63ec Log: [JENKINS-20769 JENKINS-20204] Integrating remoting 2.36 Fixed a bug Jesse found in remoting (cherry picked from commit 75447b57b655e38fdb48f1e854a4b287071342cf) Conflicts: pom.xml
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            @Kohsuke
            I still see the issue on remoting-2.36...

            java version "1.7.0_51"
            Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
            Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)

            Manifest of the slave.jar

            Manifest-Version: 1.0
            Trusted-Library: true
            Application-Name: Jenkins Remoting Agent
            Build-Jdk: 1.7.0_07
            Built-By: kohsuke
            Permissions: all-permissions
            Created-By: Apache Maven
            Main-Class: hudson.remoting.Launcher
            Version: 2.36
            Codebase: *
            Archiver-Version: Plexus Archiver

            Name: org/kohsuke/args4j/MapSetter.class
            SHA-256-Digest: tyuIM4M9anur1hStvbgsYrs+g4WqVjGY0zgPEr1z4jw=

            Name: org/jenkinsci/constant_pool_scanner/ConstantPool$1$1.class
            SHA-256-Digest: UKGAapa919i1hiZJuSy1xx7dVEgonnjgqNxghQjWDMo=

            Name: hudson/remoting/DelegatingCallable.class
            SHA-256-Digest: 3eiABqJQGmXrLl5omnmV7YOVh/r7DAh21TQa9zqYntE=

            ...

            Show
            oleg_nenashev Oleg Nenashev added a comment - @Kohsuke I still see the issue on remoting-2.36... java version "1.7.0_51" Java(TM) SE Runtime Environment (build 1.7.0_51-b13) Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode) Manifest of the slave.jar Manifest-Version: 1.0 Trusted-Library: true Application-Name: Jenkins Remoting Agent Build-Jdk: 1.7.0_07 Built-By: kohsuke Permissions: all-permissions Created-By: Apache Maven Main-Class: hudson.remoting.Launcher Version: 2.36 Codebase: * Archiver-Version: Plexus Archiver Name: org/kohsuke/args4j/MapSetter.class SHA-256-Digest: tyuIM4M9anur1hStvbgsYrs+g4WqVjGY0zgPEr1z4jw= Name: org/jenkinsci/constant_pool_scanner/ConstantPool$1$1.class SHA-256-Digest: UKGAapa919i1hiZJuSy1xx7dVEgonnjgqNxghQjWDMo= Name: hudson/remoting/DelegatingCallable.class SHA-256-Digest: 3eiABqJQGmXrLl5omnmV7YOVh/r7DAh21TQa9zqYntE= ...
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            Hmm...
            My apologies, the previous error has been caused by improper Jenkins URL in global configs => JNLP used jar from another server

            Show
            oleg_nenashev Oleg Nenashev added a comment - Hmm... My apologies, the previous error has been caused by improper Jenkins URL in global configs => JNLP used jar from another server

              People

              • Assignee:
                kohsuke Kohsuke Kawaguchi
                Reporter:
                whimboo Henrik Skupin
              • Votes:
                19 Vote for this issue
                Watchers:
                34 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: