ds123 wrote:Version 6 of redis supports TLS directly, but I am having trouble getting that to work. Their documentation emphasizes that there is a directive make BUILD_TLS=yes required.
The phrasing suggests that this would be an extra parameter passed to
make at build time. If you do not see it in the ebuild, then the default from upstream would be used. Your post suggests to me that the upstream default is
=no.
ds123 wrote:Looking in the ebuild redis-6.0.9.ebuild, nothing suggests a dependency on openssl.
Then either the ebuild dependency data is wrong, or the ebuild does not enable TLS.
ds123 wrote:When I try emerge -evp dev-db/redis, I can see that openssl is a precursor for it, so there is that.
Are you sure?
-e is short for
--emptytree, so
dev-libs/openssl would be shown if redis, or anything required by redis, depended on it. Hypothetically, redis could depend on a helper package that uses HTTPS, and that helper could need openssl in order to use HTTPS. That would then cause openssl to be shown in
-evp output, even though redis itself made no use of openssl. The simplest test, which is not perfect, but is usually right, would be to install redis and then inspect the
lddtree output for it, to see if it loads openssl, either directly or indirectly. If you do not see openssl there, then I expect it probably does not have TLS support enabled in your build.