From 4dcd6f37c697b1517b5e36ae1b9d130abfcd7699 Mon Sep 17 00:00:00 2001 From: Michael Davidsaver Date: Sun, 23 Jun 2019 16:18:43 -0700 Subject: [PATCH] update release notes --- documentation/RELEASE_NOTES.html | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/documentation/RELEASE_NOTES.html b/documentation/RELEASE_NOTES.html index 376279fc9..1d93d2b3b 100644 --- a/documentation/RELEASE_NOTES.html +++ b/documentation/RELEASE_NOTES.html @@ -38,7 +38,7 @@ host, and the IOC would believe them.

look up the IP address of any hostnames listed in its ACF (which will normally be done using the DNS or the /etc/hosts file). The IOC will then compare the resulting IP address against the client's actual IP address when -checking access permissions at connection time. This name resolution gets done +checking access permissions at connection time. This name resolution is performed at ACF file load time, which has a few consequences:

    @@ -46,14 +46,17 @@ at ACF file load time, which has a few consequences:

  1. If the DNS is slow when the names are resolved this will delay the process of loading the ACF file.
    2. -
  2. If a host name cannot be resolved the IOC will treat the ACF as invalid, -which prevents any CA clients from connecting.
    3. +
  3. If a host name cannot be resolved the IOC will proceed, but this host name +will never be matched.
  4. Any changes in the hostname to IP address mapping will not be picked up by the IOC unless and until the ACF file gets reloaded.
+

Optionally, IP addresses may be added instead of, or in addition to, host names +in the ACF file.

+

This feature can be enabled before iocInit with