From 39071ff932395fcdd3f7434ed2e5f15cdbf65fc0 Mon Sep 17 00:00:00 2001 From: Kurt Zeilenga Date: Tue, 18 Jun 2002 08:02:36 +0000 Subject: [PATCH] SSF updates --- doc/guide/admin/security.sdf | 13 ++++++------- doc/guide/preamble.sdf | 1 + 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/doc/guide/admin/security.sdf b/doc/guide/admin/security.sdf index df5714f9de..55b167565b 100644 --- a/doc/guide/admin/security.sdf +++ b/doc/guide/admin/security.sdf @@ -79,13 +79,12 @@ See the {{SECT:Using SASL}} chapter for more information. H3: Security Strength Factors -The server uses {{TERM[expand]Security Strength Factors}} (SSF) to -indicate the relative strength of protection. A SSF of zero (0) -indicates no protections are in place. A SSF of one (1) indicates -integrity protection are in place. A SSF greater than one (>1) -roughly correlates to the effective encryption key length. For -example, {{TERM:DES}} is 56, {{TERM:3DES}} is 112, and {{TERM:AES}} -128, 192, or 256. +The server uses {{TERM[expand]SSF}}s (SSF) to indicate the relative +strength of protection. A SSF of zero (0) indicates no protections +are in place. A SSF of one (1) indicates integrity protection are +in place. A SSF greater than one (>1) roughly correlates to the +effective encryption key length. For example, {{TERM:DES}} is 56, +{{TERM:3DES}} is 112, and {{TERM:AES}} 128, 192, or 256. A number of administrative controls rely on SSFs associated with TLS and SASL protection in place on an LDAP session. diff --git a/doc/guide/preamble.sdf b/doc/guide/preamble.sdf index f28c65da6d..8393672768 100644 --- a/doc/guide/preamble.sdf +++ b/doc/guide/preamble.sdf @@ -182,6 +182,7 @@ PS|Proposed Standard RDN|Relative Distinguished Name RFC|Request for Comments SRP|Secure Remote Password +SSF|Security Strength Factor SSL|Secure Socket Layer STD|Internet Standard TCP|Transmission Control Protocol -- 2.39.5