From 5833fe40996c75adcf1e116104ffe6169c4866e6 Mon Sep 17 00:00:00 2001
From: rhaggard <rhaggard@localhost>
Date: Fri, 01 Feb 2008 18:37:01 +0000
Subject: [PATCH] Uncommitting last changes to configuration .xml files, second try

---
 opends/src/admin/defn/org/opends/server/admin/std/BlindTrustManagerProviderConfiguration.xml |   10 +++++-----
 1 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/opends/src/admin/defn/org/opends/server/admin/std/BlindTrustManagerProviderConfiguration.xml b/opends/src/admin/defn/org/opends/server/admin/std/BlindTrustManagerProviderConfiguration.xml
index 37f4373..b118864 100644
--- a/opends/src/admin/defn/org/opends/server/admin/std/BlindTrustManagerProviderConfiguration.xml
+++ b/opends/src/admin/defn/org/opends/server/admin/std/BlindTrustManagerProviderConfiguration.xml
@@ -31,11 +31,11 @@
   xmlns:adm="http://www.opends.org/admin"
   xmlns:ldap="http://www.opends.org/admin-ldap">
   <adm:synopsis>
-    The blind trust manager provider always trusts any certificate that 
-    is presented to it, regardless of its issuer, subject, and validity 
-    dates. Use the blind trust manager provider only for testing 
-    purposes, because it allows clients to use forged certificates 
-    and authenticate as virtually any user in the server.
+    The
+    <adm:user-friendly-name />
+    provides a mechanism for blindly trusting any certificate presented
+    to it without performing any kind of validation, including ignoring
+    the validity dates included within the certificate.
   </adm:synopsis>
   <adm:profile name="ldap">
     <ldap:object-class>

--
Gitblit v1.10.0