Vagrant: Dynamically linked version of OpenSSL in AppImage "container" causes `vagrant ssh` to fail.

[espoelstra]

Vagrant version

Using Vagrant 2.1.1

Host operating system

Ubuntu 18.04

Guest operating system

Ubuntu 18.04/16.04/etc

Vagrantfile

Fails on 16.04, 18.04, pretty much any version because the AppImage SSL doesn't match the host.

## -*- mode: ruby -*-
## vi: set ft=ruby :

Vagrant.configure("2") do |config|
  config.vm.box = "bento/ubuntu-18.04"
   config.vm.provider "virtualbox" do |vb|
     vb.gui = true
     vb.memory = "4096"
   end
end

Debug output

Will paste if requested, issue seems pretty straightforward.

Expected behavior

I should be able to vagrant ssh without any errors when using the AppImage version of Vagrant.

AppImage is a fantastic and portable format, and I would like to use it on Ubuntu/Fedora/everywhere rather than only using it when a native package isn't available. I understand that it increases the size of the AppImage if you pull in libssl and it also means you have to release a new version if there is a security issue identified in an older version of libssl contained in the AppImage, but since they are designed to be self contained runtimes and hopefully your build process has reproducible artifacts, you should be able to bundle a version of OpenSSL and re-release the AppImage with a slightly bumped version if the libssl you include in a version is superceded.

Actual Behavior

Using AppImage version and vagrant ssh results in `OpenSSL version mismatch. Built against 100020ef, you have 1000106f``.

Steps to reproduce

1. vagrant init bento/ubuntu-18.04
2. vagrant up
3. vagrant ssh

[espoelstra]

https://github.com/openssl/openssl/issues/1631#issuecomment-250021959

https://askubuntu.com/a/830532/318507

[davidsolorzano20]

I had the same error, but I returned to vagrant 2.1.0 and fixed my error. Now it works well.

[thurt]

@davidsolorzano20 downgrading vagrant from 2.1.1 to 2.1.0 fixed my error, OpenSSL version mismatch. Built against 1000207f, you have 1000106f. how did you figure that out? links provided above don't describe anything about downgrading vagrant.

[davidsolorzano20]

@thurt I checked in 2 operating systems Ubuntu 18.04 and LinuxMint 18.3, I got the same error, I updated the openssl in both and nothing. then I decided to try an earlier version of vagrant.

[Genovo]

same error on "bento/ubuntu-16.04",

~$ vagrant ssh n4
OpenSSL version mismatch. Built against 1000207f, you have 1000106f

but downgrading to Vagrant 2.1.0 did not fix error

~$ vagrant --version
Vagrant 2.1.0

Also not related to non-Ubuntu OpenSSL issues,

~$ ldd /usr/bin/openssl
    linux-vdso.so.1 =>  (0x00007ffcdcbdc000)
    libssl.so.1.0.0 => /lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x00007f2baca45000)
    libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x00007f2bac601000)
    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f2bac237000)
    libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f2bac033000)
    /lib64/ld-linux-x86-64.so.2 (0x00007f2baccae000)

Upgraded to latest LTS OpenSSL, got same error

~$ openssl version
OpenSSL 1.0.2o  27 Mar 2018
#  It was 1.0.2g

Switched from "bento/ubuntu-16.04" to "ubuntu/xenial64" and back to Vagrant 2.1.1
Same error

not caused by a local copy of ssh

$ which ssh
/usr/bin/ssh

This error crops up a lot, saw a thread blaming py installer
https://github.com/pyinstaller/pyinstaller/issues/2237

FINALLY -- gave up on vagrant ssh -- got this answer and it worked:

vagrant ssh-config > vagrant-ssh
ssh n4 -F vagrant-ssh

https://stackoverflow.com/questions/10864372/how-to-ssh-to-vagrant-without-actually-running-vagrant-ssh

[hashibot[bot]]

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.