Docs: Mention issues with TLS client cert and Exim <= 4.85

* cb1d783072c488a4a558607b2ee122efba95aa4b
* 8c40856083f3a2e89350ab3aacfb95256fbadd9d

> Author: Jeremy Harris <jgh146exb@wizmail.org>
> Date:   Sun Nov 23 16:10:30 2014 +0000
>
>    Support use of system default CA bundle

diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt
index 74c9b083c4a28685c7cb57114f4b2013958eff83..c865e111bb125bde2427c2013964efa5a4a35e30 100644 (file)
--- a/doc/doc-docbook/spec.xfpt
+++ b/doc/doc-docbook/spec.xfpt
@@ -18489,7 +18489,9 @@ than the public cert of individual clients.  With both OpenSSL and GnuTLS, if
 the value is a file then the certificates are sent by Exim as a server to
 connecting clients, defining the list of accepted certificate authorities.
 Thus the values defined should be considered public data.  To avoid this,
 the value is a file then the certificates are sent by Exim as a server to
 connecting clients, defining the list of accepted certificate authorities.
 Thus the values defined should be considered public data.  To avoid this,

-use the explicit directory version.
+use the explicit directory version. (If your peer is Exim up to 4.85,
+using GnuTLS, you may need to send the CAs (thus using the file
+variant). Otherwise the peer doesn't send its certificate.)

 
 See &<<SECTtlssni>>& for discussion of when this option might be re-expanded.
 
 
 See &<<SECTtlssni>>& for discussion of when this option might be re-expanded.