Package: cloud.debian.org Followup-For: Bug #1011756 X-Debbugs-Cc: a.t.chadw...@gmail.com
## Workaround 2 (neater) Testing a bit more, I can confirm that installing vagrant 2.2.19 from Debian Testing fixes this on Debian 11 (buster) hosts when trying to connect to debian/testing64 box images. I guess Vagrant uses ruby-net-ssh for the initial connection using the insecure default key, the connection it uses to replace that key on the new machine with the creating user’s. This is why it also ignores config.ssh.extra_args in Vagrantfiles for that initial connection, but respects them at “vagrant ssh” time. Debian 11 users only need to update the vagrant package for now, iupdating from stable’s 2.2.14+dfsg-1 to testing’s 2.2.19+dfsg-1. They will need to employ apt pinning to stay on stable while updating vagrant from testing. One HOWTO is here: https://coderwall.com/p/aatvta/apt-pinning-in-debian, or see https://wiki.debian.org/AptConfiguration for a deeper dive. Vagrant’s written in Ruby, and it is packaged to be pretty tolerant about its dependencies’ versions in Debian. - Andrew
