Blame SOURCES/0136-MAN-Misspelled-username-in-pam_trusted_users-is-not-.patch

905b4d
From e786e081edecabb8e8506dd3c5e668094827bc52 Mon Sep 17 00:00:00 2001
905b4d
From: Jakub Hrozek <jhrozek@redhat.com>
905b4d
Date: Thu, 11 Dec 2014 11:19:58 +0100
905b4d
Subject: [PATCH 136/138] MAN: Misspelled username in pam_trusted_users is not
905b4d
 fatal
905b4d
905b4d
The man page claimed that failing to resolve an user name results in
905b4d
failure to start SSSD, but it's not the case and shouldn't be, because
905b4d
marking a user as trusted only elevates privileges, so it's safe to
905b4d
ignore that failure.
905b4d
905b4d
https://fedorahosted.org/sssd/ticket/2530
905b4d
905b4d
Reviewed-by: Pavel Reichl <preichl@redhat.com>
905b4d
---
905b4d
 src/man/sssd.conf.5.xml | 5 -----
905b4d
 1 file changed, 5 deletions(-)
905b4d
905b4d
diff --git a/src/man/sssd.conf.5.xml b/src/man/sssd.conf.5.xml
905b4d
index 3525d78caff28fd05cc18061d023fec3c50d1a47..2002ccc7caf7013ead5b97c463fba46b734090ae 100644
905b4d
--- a/src/man/sssd.conf.5.xml
905b4d
+++ b/src/man/sssd.conf.5.xml
905b4d
@@ -907,11 +907,6 @@ fallback_homedir = /home/%u
905b4d
                             the PAM responder even in case it is not in the
905b4d
                             pam_trusted_users list.
905b4d
                         </para>
905b4d
-                        <para>
905b4d
-                            Also please note that if there is a user name in
905b4d
-                            pam_trusted_users list which fails to be resolved
905b4d
-                            it will cause that SSSD will not be started.
905b4d
-                        </para>
905b4d
                     </listitem>
905b4d
                 </varlistentry>
905b4d
                 <varlistentry>
905b4d
-- 
905b4d
1.9.3
905b4d