Using LibreSSL

I also wanted to note that both OPNSense and HardenedBSD backed off using LibreSSL.
For HardenedBSD, Shawn said it was manpower issue to keep both. OPNSense was doing a version with LibreSSL for a while.
 
I used to have LibreSSL on my server and decided to switch back after some ports required OpenSSL to build. I'll wait until FreeBSD decides to switch to LibreSSL then that will force maintainers to patch their ports to use LibreSSL. In the meantime, you're better off staying with OpenSSL.
 
Yeah, I too had it set for a while. But too many ports either failed to build or had other issues. So I switched back to the base OpenSSL.
 
drhowarddrfine said:
olafz Are you sure about that? I've never used libressl with nginx.
Click to expand...
Yes.

root@annie:~ # pkg query %ro libressl
databases/mariadb103-server
lang/ruby25
databases/mariadb103-client
mail/postfix
security/php72-openssl
security/openssh-portable
security/py-cryptography
archivers/libzip
archivers/libarchive
lang/python27
ftp/curl
dns/ldns
lang/python36
www/nginx
security/p5-Net-SSLeay
devel/libevent
 
Just to clarify for people glancing at the thread, the OP has set it as default in their /etc/make.conf but it is not the default in an install of FreeBSD. (Nor do I think the OP implied it was, but a new user may get slightly confused).
 
OpenSSL has come a long way since LibreSSL was created. It now has several paid maintainers who have modernized the codebase and eliminated most of the problems that caused the LibreSSL fork. And they continue to improve it. This can be seen by the fact OpenSSL supports TLSv1.3 and LibreSSL still does not.

I stuck with LibreSSL for a couple of years but moved back to OpenSSL when 1.1.1 came out.
 
You must log in or register to reply here.
Back
Top