builder/docker/communicator.go | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 fix tails import path (project moved)

communicator/ssh/communicator_test.go | 3 3 + 0 - 0 !
1 file changed, 3 insertions(+)

 handle abi change of golang-golang-x-crypto-dev

That ABI change was due to CVE security fix

Fix is picked from upstream of golang-golang-x-crypto-dev:
  https://github.com/golang/crypto/commit/e4e2799dd7aab89f583e1d898300d96367750991

Closes: #861282

builder/amazon/common/ssh.go | 1 1 + 0 - 0 !
builder/azure/common/lin/ssh.go | 1 1 + 0 - 0 !
builder/digitalocean/ssh.go | 1 1 + 0 - 0 !
builder/googlecompute/ssh.go | 1 1 + 0 - 0 !
builder/openstack/ssh.go | 1 1 + 0 - 0 !
builder/parallels/common/ssh.go | 5 3 + 2 - 0 !
6 files changed, 8 insertions(+), 2 deletions(-)

 update ssh client usage for new crypto/ssh version

[cherry-picked ee5d13611fb8aca1f1014f9bcd65c18fffdd1b2b with modification]

builder/null/ssh.go | 1 1 + 0 - 0 !
builder/qemu/ssh.go | 5 3 + 2 - 0 !
builder/virtualbox/common/ssh.go | 5 3 + 2 - 0 !
builder/vmware/common/ssh.go | 5 3 + 2 - 0 !
4 files changed, 10 insertions(+), 6 deletions(-)

 specify insecureignorehostkey for hostkeycallback

[A recent breaking change upstream in Golang's crypto
library](https://github.com/golang/crypto/commit/e4e2799dd7aab89f583e1d898300d96367750991)
has broken SSH connectivity for a few builders:

```
==> qemu: Waiting for SSH to become available...
2017/05/20 16:23:58 ui: ==> qemu: Waiting for SSH to become available...
2017/05/20 16:23:58 packer: 2017/05/20 16:23:58 [INFO] Attempting SSH connection...
2017/05/20 16:23:58 packer: 2017/05/20 16:23:58 reconnecting to TCP connection for SSH
2017/05/20 16:23:58 packer: 2017/05/20 16:23:58 handshaking with SSH
2017/05/20 16:23:58 packer: 2017/05/20 16:23:58 handshake error: ssh: must specify HostKeyCallback
2017/05/20 16:23:58 packer: 2017/05/20 16:23:58 [DEBUG] SSH handshake err: ssh: must specify HostKeyCallback
2017/05/20 16:24:05 packer: 2017/05/20 16:24:05 [INFO] Attempting SSH connection...
2017/05/20 16:24:05 packer: 2017/05/20 16:24:05 reconnecting to TCP connection for SSH
2017/05/20 16:24:05 packer: 2017/05/20 16:24:05 handshaking with SSH
2017/05/20 16:24:05 packer: 2017/05/20 16:24:05 handshake error: ssh: must specify HostKeyCallback
2017/05/20 16:24:05 packer: 2017/05/20 16:24:05 [DEBUG] SSH handshake err: ssh: must specify HostKeyCallback
```

Specifying HostKeyCallback as insecure should make things work again
and would make sense for packer's use case.

[cherry-picked a0052fdb687f80ac07e67d7a0f39dcf3a66e32dd with modification]