[28348] in CVS-changelog-for-Kerberos-V5
krb5 commit: Change example module name in host_config.rst
daemon@ATHENA.MIT.EDU (Greg Hudson)
Sun Jun 1 00:35:10 2014
Date: Sun, 1 Jun 2014 00:35:05 -0400
From: Greg Hudson <ghudson@mit.edu>
Message-Id: <201406010435.s514Z5Nq012385@drugstore.mit.edu>
To: cvs-krb5@mit.edu
Reply-To: krbdev@mit.edu
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cvs-krb5-bounces@mit.edu
https://github.com/krb5/krb5/commit/26a43afbc214e8d24cf261f245007192eccb7ed5
commit 26a43afbc214e8d24cf261f245007192eccb7ed5
Author: Greg Hudson <ghudson@mit.edu>
Date: Tue May 27 13:01:49 2014 -0400
Change example module name in host_config.rst
Don't use "otp" as the example clpreauth module name in
host_config.rst, since we now ship an effectively built-in otp
clpreauth module. Instead use "mypreauth".
ticket: 7920 (new)
target_version: 1.12.2
tags: pullup
doc/admin/host_config.rst | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/admin/host_config.rst b/doc/admin/host_config.rst
index 2ac12ad..4bea576 100644
--- a/doc/admin/host_config.rst
+++ b/doc/admin/host_config.rst
@@ -27,12 +27,12 @@ and the path to the module, separated by a colon. The module name
will often be the same as the shared object's name, but in unusual
cases (such as a shared object which implements multiple modules for
the same interface) it might not be. For example, to register a
-client preauthentication module named ``otp`` installed at
-``/path/to/otp.so``, you could write::
+client preauthentication module named ``mypreauth`` installed at
+``/path/to/mypreauth.so``, you could write::
[plugins]
clpreauth = {
- module = otp:/path/to/otp.so
+ module = mypreauth:/path/to/mypreauth.so
}
Many of the pluggable behaviors in MIT krb5 contain built-in modules
_______________________________________________
cvs-krb5 mailing list
cvs-krb5@mit.edu
https://mailman.mit.edu/mailman/listinfo/cvs-krb5
