-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
Encrypted SSH Keys #73
Comments
Not sure if you'd want to attack this but it definitely was a big "what?" error. |
Yeah so I tagged this as a bug. I think in the short term we at least want to show a better error. I'm not sure how to handle this well with automation and the hands-off approach Terraform takes. Any ideas? |
@mitchellh I ran into this issue as well. If terraform is run by an actual person, won't using ssh-agent basically solve this problem? |
@michiels Maybe that is a good solution. Maybe the solution is simply a better error message that says to either unencrypt it for the duration of the run or to use an SSH-agent. I like it! Thoughts? |
I'm a fan of a better error message for now. 👍 |
Fixed |
Awesome. Thanks Mitchell. On Tuesday, August 5, 2014, Mitchell Hashimoto [email protected]
|
I want to make sure I understand: terraform does not support ssh-agent forwarding or local, or keys with passwords yet |
@hh @mitchellh that's my understanding as well. It's a real shame, as I don't use any passwordless private keys. To clarify: I tried setting
However, I am able to ssh manually. Of course I could not set update turns out I left the host field blank, so that was the issue for me. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
When using
key_file
to choose which key to use for connection / provisioning on SSH I used a key that was encrypted and the error message was very... cryptic. (pun intended).Reference: https://code.google.com/p/go/issues/detail?id=6650
Excerpt
The text was updated successfully, but these errors were encountered: