-
-
Notifications
You must be signed in to change notification settings - Fork 637
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ssh plugin 1.16 requires needs a host verification strategy set. #589
Comments
Is there is a link to the change in the upstream code we could reference? |
I found the following links in case they would be useful. Jenkins Bug Report SSH Slave Plugin Update |
There is a new method definition for I've been able to patch https://github.com/chef-cookbooks/jenkins/blob/master/libraries/slave_ssh.rb#L103-L120 to the below, which changes the default configuration for the agent.
We could create a property for the Verification Strategy (and possibly jdkInstaller) and translate that into the class name, instead of the |
Howdy, Is there any update on this? It would be helpful in my environment; I'd rather not keep around a local monkey-patched jenkins cookbook. Thanks much, |
Hello, This issue is still active, preventing creation on new jenkins agent. Can you please look on this problem? ERROR: Unexpected exception occurred while performing groovy command. |
As an FYI I tried many things to get the example that Josh provided to work for me. Also, thank you Josh! Posting this below in case that helps anyone. See . In my case it was failing because of the "com.cloudbees.plugins.credentials.impl.UsernamePasswordCredentialsImpl" I just directly set the credId and that seemed to at least get me unblocked. `def launcher_groovy
|
Cookbook version
5.0.0
Chef-client version
12.18
Platform Details
Jekins 2.32
ssh-slaves plugin 1.16
Scenario:
Adding ssh Slaves
Steps to Reproduce:
Create an ssh with version 1.15 or higher of the ssh-slaves plug-in
Expected Result:
Slave created with no errors or warnings
Actual Result:
Slave is created successfully, but Jenkins posts a Security warning saying:
SSH Host Key Verifiers are not configured for all SSH slaves on this Jenkins instance. This could leave these slaves open to man-in-the-middle attacks. Update your slave configuration to resolve this.
The text was updated successfully, but these errors were encountered: