From: Jeremy Harris Date: Wed, 12 Oct 2016 12:40:19 +0000 (+0100) Subject: Docs: add warning on SNI-dependent certfile expansion needing a good default X-Git-Tag: exim-4_88_RC3~37 X-Git-Url: https://vcs.fsf.org/?a=commitdiff_plain;h=4233fe0a33ed8dba34764472af7ac224321cb53d;p=exim.git Docs: add warning on SNI-dependent certfile expansion needing a good default --- diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt index 97df293d5..45d845718 100644 --- a/doc/doc-docbook/spec.xfpt +++ b/doc/doc-docbook/spec.xfpt @@ -27537,8 +27537,13 @@ during TLS session handshake, to permit alternative values to be chosen: Great care should be taken to deal with matters of case, various injection attacks in the string (&`../`& or SQL), and ensuring that a valid filename -can always be referenced; it is important to remember that &$tls_sni$& is +can always be referenced; it is important to remember that &$tls_in_sni$& is arbitrary unverified data provided prior to authentication. +.new +Further, the initial cerificate is loaded before SNI is arrived, so +an expansion for &%tls_certificate%& must have a default which is used +when &$tls_in_sni$& is empty. +.wen The Exim developers are proceeding cautiously and so far no other TLS options are re-expanded.