Date: Fri, 12 May 2023 02:23:26 +0100 From: Jamie Landeg-Jones <jamie@catflap.org> To: yaneurabeya@gmail.com, bofh@FreeBSD.org Cc: vishwin@FreeBSD.org, portmgr@FreeBSD.org, freebsd-arch@FreeBSD.org, emaste@FreeBSD.org, cy@FreeBSD.org, brnrd@FreeBSD.org Subject: Re: OpenSSL 3.0 for 14.0-RELEASE: issues with 1.x/3.x symbol clashing, ports linking against base OpenSSL, ports that don't compile/link against OpenSSL 3, etc Message-ID: <202305120123.34C1NQsB002454@donotpassgo.dyslexicfish.net> In-Reply-To: <4733AD1A-7954-4B79-9789-A57A0B46C71B@freebsd.org> References: <C6F8DD52-348E-42D8-84DE-B3A399D2606F@gmail.com> <A8A165FF-1C53-40BE-88B8-D18D11F77DDD@freebsd.org> <4733AD1A-7954-4B79-9789-A57A0B46C71B@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Moin Rahman <bofh@FreeBSD.org> wrote: > I have completed my final partial exp-run with ports that has USES=ssl in any form and the result is available from here: > https://pkg.bofh.network/build.html?mastername=MAIN-default-openssl3&build=2023-05-04_16h25m58s I noticed that security/sslscan isn't on that list, presumably because its reliance on SSL is conditional: | UNSAFESSL_USES_OFF= ssl In addition, it is already marked as failing unless built specifically against openssl-unsafe. | .if empty(PORT_OPTIONS:MUNSAFESSL) && ${SSL_DEFAULT:Mopenssl} | BROKEN= Does not build with openssl | .endif For what it's worth, I updated, and fixed this port to work with openssl 3.1.0 (it needs to compile it statically to retain the full functionality without requiring "openssl-unsafe" to be installed.) The updated version removes any requirement for USES=ssl at all. PR has gone through maintainer-timeout but no-one is picking it up. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270101 Cheers, Jamie
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202305120123.34C1NQsB002454>