Craig Anderson

Sure, that sounds reasonable. I'll take a look and get back to you.

@ooglek did you ever figure out a way to use something like GetAllLookupValues() in 2.0?

@steveheinsch Thanks for that gist, very helpful. @ooglek Thanks for letting me know.

Perhaps you could contribute then.

This is probably an uninformed question since I know very little about this kind of stuff, but is it possible to force Ubuntu to use a newer version of OpenSSL...

I just updated to the latest Homestead and Base box and still experience the problem. The updated output of `vagrant destroy` and `vagrant up` can be seen [here](https://gist.github.com/intrepidws/3a4690e813c9ed029c9d7ccdbc004675). In my...

> This could be something we build into a script and have Homestead do via a configuration flag/option/etc. Assuming we could reliably script the recompile. I always tried to avoid...

I tried [these instructions](https://medium.com/@brunoosiek/updating-openssl-latest-and-greatest-version-in-ubuntu-18-04-8f10ba4e2377) to upgrade the OpenSSL version myself, but always get the following error when I try to run `openssl version` after I'm done: > openssl: symbol lookup...

It appears that there is a [workaround](https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1951279/comments/17), where you disable a specific cipher (CHACHA20) that is causing the problem. Here is the proof of concept to run from the command...

> Detailed info in my gist: [How to compile OpenSSL to the 1.1.1m version in after.sh file](https://gist.github.com/elcheco/d7eebcaa8bb2b8afb6171a9ce24e923a) @elcheco The gist link does not work.