Skip to content
This repository has been archived by the owner on May 23, 2020. It is now read-only.

Cleanup imports #1

Merged
merged 3 commits into from Nov 27, 2018
Merged

Cleanup imports #1

merged 3 commits into from Nov 27, 2018

Conversation

Ajibola
Copy link

@Ajibola Ajibola commented Nov 10, 2017

updated github urls from mitchellh to hashicorp as it caused some build problems when installing the linode plugin

@Ajibola
Copy link
Author

Ajibola commented Nov 29, 2017

@dradtke hi, could you please review PR? Thanks.

@@ -12,6 +12,7 @@ func commHost(state multistep.StateBag) (string, error) {
func sshConfig(state multistep.StateBag) (*ssh.ClientConfig, error) {
return &ssh.ClientConfig{
User: "root",
HostKeyCallback: ssh.InsecureIgnoreHostKey(),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything looks good, except I think this line shouldn't be the default. It can certainly be made configurable, though.

Apologies for the delay on this.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok true, will work on generating the hostkey if passed in.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Being able to specify an SSH key to verify against is a good idea, but I also think the insecure option should be strictly opt-in, e.g. "ssh_insecure": true. If neither is provided, it would use the current behavior, which is to not specify a value for HostKeyCallback at all.

Copy link
Author

@Ajibola Ajibola Nov 30, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not specifying HostKeyCallback will automatically fail on latest Go version since the behaviour has been changed, according to golang/go#19767

Insecure is the same as not specifying AFAIK. This should be the default, as was previously, but I understand ensuring that a user explicitly states that they want to use the insecure mode.

Is it ok for the connection attempt to fail if "ssh_insecure":true is not set?

@dradtke dradtke merged commit d29b283 into linode:master Nov 27, 2018
displague added a commit that referenced this pull request Feb 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants