[krbdev.mit.edu #8831] git commit

"Greg Hudson via RT" <[email protected]>
Newsgroups gmane.comp.encryption.kerberos.bugs
Message-ID <[email protected]>
Thu Sep 19 17:10:16 2019: Request 8831 was acted upon.
 Transaction: Ticket created by [email protected]
       Queue: krb5
     Subject: git commit
       Owner: [email protected]
  Requestors: 
      Status: new
 Ticket <URL: https://krbdev.mit.edu/rt/Ticket/Display.html?id=8831 >



Update LDAP KDB module documentation

Remove ldapbackend.rst, as it is largely redundant with conf_ldap.rst.

Simplify conf_ldap.rst, using kerberos.openldap.ldif (added by ticket
8529) and removing unnecessary command arguments.  Mention the
possibility of using SASL authentication (added by ticket 7944) as an
alternative to binding with DN and password.  Remove unnecessary
access rights.

In kdc_conf.rst, remove ldap_servers from the list of relations read
from [dbdefaults], as it is only read from the realm's database
configuration section.

In kdb5_ldap_util.rst, document "-r" as a global parameter, as it
applies in some fashion to all commands.  Make the same changes to the
kdb5_ldap_util usage message, and make it fit within 80 columns.

Reported by Dilyan Palauzov.

https://github.com/krb5/krb5/commit/ca1057fe6a03b6679b7907ee41b8abd444acc70d
Author: Greg Hudson <[email protected]>
Commit: ca1057fe6a03b6679b7907ee41b8abd444acc70d
Branch: master
 doc/admin/admin_commands/kdb5_ldap_util.rst     |   84 +++++--------
 doc/admin/advanced/index.rst                    |    1 -
 doc/admin/advanced/ldapbackend.rst              |  143 -----------------------
 doc/admin/conf_files/kdc_conf.rst               |    1 -
 doc/admin/conf_ldap.rst                         |  134 ++++++++-------------
 src/man/kdb5_ldap_util.man                      |   94 ++++++----------
 src/man/kdc.conf.man                            |   13 +-
 src/plugins/kdb/ldap/ldap_util/kdb5_ldap_util.c |   34 +++---
 8 files changed, 144 insertions(+), 360 deletions(-)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.