Date: Tue, 20 Apr 1999 10:14:57 -0700 (PDT) From: paxvel@iname.com To: freebsd-gnats-submit@freebsd.org Subject: ports/11237: port security/stunnel broken (wants rsaref) Message-ID: <19990420171457.2915715407@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 11237
>Category: ports
>Synopsis: port security/stunnel broken (wants rsaref)
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-ports
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Tue Apr 20 10:20:01 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator: Pavel Andreev
>Release: FreeBSD 3.1-STABLE
>Organization:
VUMS software, Czech Republic
>Environment:
FreeBSD astra.vumsoft.cz 3.1-STABLE FreeBSD 3.1-STABLE #9: Wed Apr 14 20:37:14 CEST 1999 paxvel@astra.vumsoft.cz:/usr/src/sys/compile/ASTRA i386
>Description:
in security/stunnel/Makefile, there is
LIB_DEPENDS= rsaref.2:${PORTSDIR}/security/rsaref
line, and in security/stunnel/patches/patch-aa, there is
LIBS=@LIBS@ -L$(PREFIX)/lib -lssl -lcrypto -lRSAglue -lrsaref
line. these lines prevent non-us users from building the port.
"make" even fetches the rsaref source, i wonder if this fetching is not
a violation of some law.
>How-To-Repeat:
cd /usr/ports/security/stunnel; make
>Fix:
remove the offending line from the Makefile
remove the "-lrsaref" from the patch
i believe openssl has anything stunnel needs, and this will work for
u.s. users too.
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990420171457.2915715407>