From 58caa2f8877d0c8562932fe063c401b0be9c19c6 Mon Sep 17 00:00:00 2001 From: Quanah Gibson-Mount Date: Thu, 18 Feb 2021 19:47:36 +0000 Subject: [PATCH] ITS#8835 - Update to use rehash command from OpenSSL --- doc/guide/admin/tls.sdf | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/guide/admin/tls.sdf b/doc/guide/admin/tls.sdf index 8bbf7b7867..1e2a8bfce8 100644 --- a/doc/guide/admin/tls.sdf +++ b/doc/guide/admin/tls.sdf @@ -81,10 +81,10 @@ H4: TLSCACertificatePath This directive specifies the path of a directory that contains individual {{TERM:CA}} certificates in separate files. In addition, -this directory must be specially managed using the OpenSSL {{c_rehash}} -utility. When using this feature, the OpenSSL library will attempt to +this directory must be specially managed using the OpenSSL {{rehash}} +command. When using this feature, the OpenSSL library will attempt to locate certificate files based on a hash of their name and serial number. -The {{c_rehash}} utility is used to generate symbolic links with the +The OpenSSL {{rehash}} command is used to generate symbolic links with the hashed names that point to the actual certificate files. As such, this option can only be used with a filesystem that actually supports symbolic links. In general, it is simpler to use the @@ -226,8 +226,8 @@ same considerations apply. H4: TLS_CACERTDIR This is equivalent to the server's {{EX:TLSCACertificatePath}} option. The -specified directory must be managed with the OpenSSL {{c_rehash}} -utility as well. +specified directory must be managed with the OpenSSL {{rehash}} +command as well. H4: TLS_CERT