https://bugs.exim.org/show_bug.cgi?id=2350
--- Comment #3 from Torsten Tributh ---
Haven't recognized this difference between TLS 1.2 and TLS 1.3 before.
Seems like stapling was not intended in the beginning to be offered from
clients also. If it will be offered in TLS 1.3 implementations there
https://bugs.exim.org/show_bug.cgi?id=2350
--- Comment #2 from Jeremy Harris ---
I note that the original RFC for stapling, 6066, only talks about it in terms
of the client requesting and the server supplying certificate status.
https://tools.ietf.org/html/rfc6066 Section 8.
Also the OpenSSL
https://bugs.exim.org/show_bug.cgi?id=2350
Jeremy Harris changed:
What|Removed |Added
Priority|medium |high
Severity|bug
On 14/12/2018 15:24, Paul Hecker via Exim-dev wrote:
> can no longer compile this version with my current Makefile as there is
>
> WITH_CONTENT_SCAN=yes
>
> enabled and all other scanner interfaces disabled (as DISABLE_MAL_CLAM=yes,
> DISABLE_MAL_AVAST=yes etc.).
>
> The error at compile-time
https://bugs.exim.org/show_bug.cgi?id=2224
--- Comment #10 from Jeremy Harris ---
Exim does not currently support the BINARYMIME extension. That is distinct
from the CHUNKING extension even though both are defined by RFC 3030.
This is not a signing bug in Exim, and if Postfix can emit such a
Hi,
can no longer compile this version with my current Makefile as there is
WITH_CONTENT_SCAN=yes
enabled and all other scanner interfaces disabled (as DISABLE_MAL_CLAM=yes,
DISABLE_MAL_AVAST=yes etc.).
The error at compile-time is
gcc -DMACRO_PREDEF malware.c
malware.c:52:2: error: empty
