From a48159f8cfbf040f46c9c79d43177664c8c412de Mon Sep 17 00:00:00 2001 From: John Date: Wed, 6 Jan 2021 18:18:49 +0100 Subject: [PATCH] stunnel: rebuild against OpenSSL --- srcpkgs/stunnel/template | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/srcpkgs/stunnel/template b/srcpkgs/stunnel/template index e3f5a07353d..54ecff002a0 100644 --- a/srcpkgs/stunnel/template +++ b/srcpkgs/stunnel/template @@ -1,11 +1,11 @@ # Template file for 'stunnel' pkgname=stunnel version=5.46 -revision=4 +revision=5 build_style=gnu-configure configure_args="--enable-ipv6 --with-ssl=${XBPS_CROSS_BASE}/usr" hostmakedepends="perl" -makedepends="libressl-devel" +makedepends="openssl-devel" checkdepends="nmap procps-ng" short_desc="SSL encryption wrapper" maintainer="Toyam Cox " @@ -34,7 +34,7 @@ post_install() { # One thing OpenBSD does that we don't do here is add a _stunnel user/group and # modify the configuration samples to chroot and use this by default. # As of 5.38 the signature expected for the CRYPTO_set_mem_functions seems to -# be out of line with what libressl provides. +# be out of line with what openssl provides. # LibreSSL wants 'void (*)(void *)' but argument is of type 'void (*)(void *, const char *, int)' # This is probably not a security problem. EDIT: Well, it would break. Badly. # --