From: Matthias A. <mat...@gm...> - 2022-04-06 17:49:38
|
Am 06.04.22 um 00:59 schrieb ckeader via Fetchmail-users: > HACK ALERT > > ... > All going well, the build completes and prints the location of the resulting > rpms. There should be three packages, binary for your %arch, SRPM and > debuginfo. The included fetchmail binary is statically linked against > openssl 3.x. It is completely untested and may not even work. In particular, > the ephemeral locations of SSL engines and modules are built into the openssl > libraries, and I do not know if fetchmail tries to load any of them in > operation; which will fail. That depends on the system's configuration. Fetchmail by itself tries to slurp the default X.509 trust store only. Purpose is that is has something to verify server certificates. fetchmail -V queries and prints the OPENSSLDIR so that there is some anchor point where people should start looking for OpenSSL's *.cnf files. However, linking something against static libraries is bad practice and you cannot update fetchmail and OpenSSL independently, and is unnecessary. Just install your local openssl 3 into some other directory, tie your fetchmail RPM to it by some file path, and make fetchmail use that with the ways shown here on the list before. Also, there is no such thing as fetchmail-7.0.0-alpha10 currently (no tag, no release). |