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

Remoting should check the "Remoting-Minimum-Version" header when connecting to the master

    • Remoting 3.32, jenkins-2.182

      It is a follow-up to JENKINS-48766. https://github.com/jenkinsci/jenkins/commit/dbc75125c565905a9c07b0c83d6ae71b2681c67f in Jenkins 2.104+ exposes the "Remoting-Minimum-Version" header.

      It would be great if Remoting verifies this header during the connection and refuses to connect if the version is not supported. If the header is missing, the connection should proceed without a warning.

          [JENKINS-50095] Remoting should check the "Remoting-Minimum-Version" header when connecting to the master

          Daniel Beck added a comment -

          Core side done in 2.171.

          Daniel Beck added a comment - Core side done in 2.171.

          Jeff Thompson added a comment -

          Released in Remoting 3.32. Not yet integrated into Jenkins.

          Jeff Thompson added a comment - Released in Remoting 3.32. Not yet integrated into Jenkins.

            vulong237 Long Nguyen
            oleg_nenashev Oleg Nenashev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: