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

set StrictHostKeyChecking=no even when no credentials are provided

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Won't Do
    • Icon: Minor Minor
    • git-client-plugin
    • None

      Given a job being configured, when a user enters a ssh clone url for a new server, the validation form will complain about Host key verification failed..
      Usually the user will then configure a set of credentials. If they are correct, the validation will succeed. If they are incorrect, the error will be Permission denied (publickey).

      The current implementation currently pass StrictHostKeyChecking=no as soon as some SSH credentials are provided, but not when no (or non-ssh) credentials are provided. It will then lead to this inconsistent error message which misleads the user into thinking something is wrong with the known_hosts file.

      In a freestyle job context this is usually very minor as the validation will provide a quick fail, however in a workflow context where the configuration is provided through free text or from scm, this can lead to confusion.

      Therefore, I'm proposing to provide this option to every ssh call through git, so that the error message is consistent.

            Unassigned Unassigned
            vlatombe Vincent Latombe
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: