Skip to content
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

Configure the ssh client library HostKeyCallback ssh.InsecureIgnoreHostKey #149

Open
rgl opened this issue Sep 22, 2021 · 3 comments
Open

Comments

@rgl
Copy link
Contributor

rgl commented Sep 22, 2021

Describe the bug

sshConfig.HostKeyCallback = ssh.InsecureIgnoreHostKey()

This code is unconditionally trusting the server without any verification, which is not, IMHO, a good default.

Expected behavior

Expect the used SSH client to inherit my ssh settings (e.g. the known_hosts file) by default.

A provider option should be provided to explicitly opt-out of the server verification, e.g.:

provider "esxi" {
  insecure = true
}

Ideally it should be configured alike a terraform provisioner connection.

@josenk
Copy link
Owner

josenk commented Sep 22, 2021

Yes, I agree. It would be a much better default. I'll try to get some time to add this feature...

@josenk
Copy link
Owner

josenk commented Nov 6, 2021

Thinking about this a bit...
To tighten up security, I should also remove the "--noSSLVerify" option for ovftool. How many home users actually have real SSL certs installed on their ESXi servers???

I'll keep all of this in mind. I may just tie them both together as a "high security enabled" option, or something like that... If there's more demand, I'll put some priority on it. Thanks for the feedback!

@jauderho
Copy link
Contributor

+1 to this request.

FWIW, I do use a real cert (Let's Encrypt) for my ESXi server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants