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

Jamie Landeg-Jones <[email protected]>
Newsgroups gmane.os.freebsd.architechture
Organization Dyslexic Fish
Message-ID <[email protected]>
Moin Rahman <[email protected]> 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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.