I have uploaded Exim 4.80 RC2 to:
ftp://ftp.exim.org/pub/exim/exim4/test/
The changes since RC1 are minor: the new SPF record support in dnsdb now
defaults to joining strings in the way dictated by the SPF
specification, instead of matching the TXT defaults; some header
corruption in the EXPERIMENTAL_DCC support has been fixed (and said
support has been documented in experimental-spec.txt -- it's not new
with 4.80, was just under-documented); some issues highlighted by clang
static analysis have been resolved; the test suite has been fixed after
I forgot to update the OpenSSL tests when I generated new test
certificates to replace the old MD5 ones.
It's worth re-emphasising the most significant non-backwards-compatible
change of this release: GnuTLS no longer supports MD5 in certificates.
If you still have such ancient beasts around, you're very overdue for
fixing that! Practical real-world attacks against MD5-based
certificates have been demonstrated, undermining the PKI trust model.
If your certificates are self-signed, generate new ones. If they are
from a Certificate Authority, a re-issue using a current CA cert should
be free (part of the price paid for the original cert and the ongoing
service associated with it). If not, switch to a CA who care about
working with you for your security.
The ChangeLog/NewStuff/README.UPDATING can be reviewed at:
http://git.exim.org/exim.git/blob/exim-4_80_RC2:/doc/doc-txt/ChangeLog
http://git.exim.org/exim.git/blob/exim-4_80_RC2:/doc/doc-txt/NewStuff
http://git.exim.org/exim.git/blob/exim-4_80_RC2:/src/README.UPDATING
The files are signed with the PGP key 0x3903637F, which has a uid
"Phil Pennock <pdp@???>". Please use your own discretion in
assessing what trust paths you might have to this uid.
Please report issues in reply to this email, on exim-users.
Thank you for your testing and feedback,
-Phil Pennock, pp The Exim Maintainers.
