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

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

    Details

    • Similar Issues:
    • Released As:
      Remoting 3.32, jenkins-2.182

      Description

      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.

        Attachments

          Issue Links

            Activity

            oleg_nenashev Oleg Nenashev created issue -
            oleg_nenashev Oleg Nenashev made changes -
            Field Original Value New Value
            Link This issue relates to JENKINS-48766 [ JENKINS-48766 ]
            oleg_nenashev Oleg Nenashev made changes -
            Labels compatibility diagnostics newbie-friendly
            oleg_nenashev Oleg Nenashev made changes -
            Summary Jenkins agent should Remoting should check the
            oleg_nenashev Oleg Nenashev made changes -
            Summary Remoting should check the Remoting should check the "Remoting-Minimum-Version" header when connecting to the master
            oleg_nenashev Oleg Nenashev made changes -
            Description 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.
            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.
            gautamabhishek46 Abhishek Gautam made changes -
            Assignee Abhishek Gautam [ gautamabhishek46 ]
            vulong237 Long Nguyen made changes -
            Assignee Abhishek Gautam [ gautamabhishek46 ] Long Nguyen [ vulong237 ]
            danielbeck Daniel Beck made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            danielbeck Daniel Beck made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            jthompson Jeff Thompson made changes -
            Status In Review [ 10005 ] Fixed but Unreleased [ 10203 ]
            Resolution Fixed [ 1 ]
            Released As Remoting 3.32
            danielbeck Daniel Beck made changes -
            Status Fixed but Unreleased [ 10203 ] Resolved [ 5 ]
            Released As Remoting 3.32 Remoting 3.32, jenkins-2.182

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: