1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
|
OpenSSL
=======
The OpenSSL Project documents their supported releases at
<https://www.openssl.org/policies/releasestrat.html>. The Exim
Maintainers are unwilling to try to support Exim built with a
version of a critical security library which is unmaintained.
Thus as versions of OpenSSL become unsupported by OpenSSL, they become
unsupported by Exim. Exim might build with older releases of OpenSSL,
but that's risky behaviour.
If your operating system vendor continues to ship an older version of
OpenSSL and is diligently backporting security fixes, and they support
Exim, then they will be backporting fixes to their packages of Exim too.
If you wish to stick purely to packages of OpenSSL, then stick to
packages of Exim too.
If someone maintains "backports", that is worth exploring too.
Note that a number of OSes use Exim with GnuTLS, not OpenSSL.
Otherwise, assuming that your operating system has old OpenSSL, and you
wish to use current Exim with OpenSSL, then you need to build and
install your own, without interfering with the system libraries.
Fortunately, this is easy.
So this only applies if you build Exim yourself.
Build
-----
Extract the current source of OpenSSL. Change into that directory.
This assumes that `/opt/openssl` is not in use. If it is, pick
something else. `/opt/exim/openssl` perhaps.
./config --prefix=/opt/openssl --openssldir=/etc/ssl \
-L/opt/openssl/lib -Wl,-R/opt/openssl/lib \
enable-ssl-trace
make
make install
You now have an installed OpenSSL under /opt/openssl which will not be
used by any system programs.
When you copy `src/EDITME` to `Local/Makefile` to make your build edits,
choose the pkg-config approach in that file, but also tell Exim to add
the relevant directory into the rpath stamped into the binary:
SUPPORT_TLS=yes
USE_OPENSSL_PC=openssl
EXTRALIBS_EXIM=-ldl -Wl,-rpath,/opt/openssl/lib
The -ldl is needed by OpenSSL 1.1+ on Linux and is not needed on most
other platforms.
Then tell pkg-config how to find the configuration files for your new
OpenSSL install, and build Exim:
export PKG_CONFIG_PATH=/opt/openssl/lib/pkgconfig
make
sudo make install
(From Exim 4.89, you can put that `PKG_CONFIG_PATH` directly into
your `Local/Makefile` file.)
Confirming
----------
Run:
exim -d-all+expand --version
and look for the `Library version: OpenSSL:` lines.
To look at the libraries _probably_ found by the linker, use:
ldd $(which exim) # most platforms
otool -L $(which exim) # MacOS
although that does not correctly handle restrictions imposed upon
executables which are setuid.
If the `chrpath` package is installed, then:
chrpath -l $(which exim)
will show the DT_RPATH stamped into the binary.
Your `binutils` package should come with `readelf`, so an alternative
is to run:
readelf -d $(which exim) | grep RPATH
Very Advanced
-------------
You can not use $ORIGIN for portably packing OpenSSL in with Exim with
normal Exim builds, because Exim is installed setuid which causes the
runtime linker to ignore $ORIGIN in DT_RPATH.
_If_ following the steps for a non-setuid Exim, _then_ you can use:
EXTRALIBS_EXIM=-ldl '-Wl,-rpath,$$ORIGIN/../lib'
The doubled `$$` is needed for the make(1) layer and the quotes needed
for the shell invoked by make(1) for calling the linker.
Note that this is sufficiently far outside normal that the build-system
doesn't support it by default; you'll want to drop a symlink to the lib
directory into the Exim release top-level directory, so that lib exists
as a sibling to the build-$platform directory.
|
