From f5bc8171a0d05300dab7eac9565f8373d588f53a Mon Sep 17 00:00:00 2001
From: Tyler Langlois <tjl@byu.net>
Date: Tue, 5 Mar 2024 15:28:37 -0700
Subject: [PATCH] vagrant: add openssl to buildInputs

See inline comment for reasoning; presence of openssl appears to be a
requisite for some libraries to function correctly.
---
 pkgs/development/tools/vagrant/default.nix | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/pkgs/development/tools/vagrant/default.nix b/pkgs/development/tools/vagrant/default.nix
index 49892f2f6c5b..cfd8d91f10cf 100644
--- a/pkgs/development/tools/vagrant/default.nix
+++ b/pkgs/development/tools/vagrant/default.nix
@@ -1,5 +1,6 @@
 { stdenv, lib, fetchurl, buildRubyGem, bundlerEnv, ruby, libarchive
 , libguestfs, qemu, writeText, withLibvirt ? stdenv.isLinux
+, openssl
 }:
 
 let
@@ -50,6 +51,11 @@ in buildRubyGem rec {
   dontBuild = false;
   src = fetchurl { inherit url hash; };
 
+  # Some reports indicate that some connection types, particularly
+  # WinRM, suffer from "Digest initialization failed" errors. Adding
+  # openssl as a build input resolves this runtime error.
+  buildInputs = [ openssl ];
+
   patches = [
     ./unofficial-installation-nowarn.patch
     ./use-system-bundler-version.patch