Attachment 692937 Details for Bug 907200 – Removing deprecated Kerberos daemon and other text.

[patch] Removing deprecated Kerberos daemon and other text.

0002-Removed-Kerberos-daemons-that-no-longer-exist-per-BZ.patch (text/plain), 3.47 KB, created by Eric Christensen on 2013-02-04 18:23:33 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Eric Christensen

Created: 2013-02-04 18:23:33 UTC

Size: 3.47 KB

patch

obsolete

>From b8b53e91d846488510331f2f973289f94ebc45e6 Mon Sep 17 00:00:00 2001
>From: Eric H Christensen <sparks@redhat.com>
>Date: Mon, 4 Feb 2013 13:21:10 -0500
>Subject: [PATCH 2/2] Removed Kerberos daemons that no longer exist per BZ 907200
>
>---
> en-US/Kerberos.xml |    8 ++++----
> 1 files changed, 4 insertions(+), 4 deletions(-)
>
>diff --git a/en-US/Kerberos.xml b/en-US/Kerberos.xml
>index 6ff2845..e15b872 100644
>--- a/en-US/Kerberos.xml
>+++ b/en-US/Kerberos.xml
>@@ -345,7 +345,7 @@
> 				<para>
> 					Create the database using the <command>kdb5_util</command> utility from a shell prompt:
> 				</para>
>-<screen>/usr/kerberos/sbin/kdb5_util create -s</screen>
>+<screen>/usr/sbin/kdb5_util create -s</screen>
> 				<para>
> 					The <command>create</command> command creates the database that stores keys for the Kerberos realm. The <command>-s</command> switch forces creation of a <firstterm>stash</firstterm> file in which the master server key is stored. If no stash file is present from which to read the key, the Kerberos server (<command>krb5kdc</command>) prompts the user for the master server password (which can be used to regenerate the key) every time it starts.
> 				</para>
>@@ -378,7 +378,7 @@
> 				</para>
> <screen>/sbin/service krb5kdc start
> /sbin/service kadmin start
>-/sbin/service krb524 start</screen>
>+</screen>
> 			</step>
> 			<step>
> 				<para>
>@@ -392,7 +392,7 @@
> 				<note>
> 					<title>Note</title>
> 					<para>
>-						By default, <command>kinit</command> attempts to authenticate using the same system login username (not the Kerberos server). If that username does not correspond to a principal in the Kerberos database, <command>kinit</command> issues an error message. If that happens, supply <command>kinit</command> with the name of the correct principal as an argument on the command line (<command>kinit <replaceable>&lt;principal&gt;</replaceable></command>).
>+						By default, <command>kinit</command> attempts to authenticate using the same system login username. If that username does not correspond to a principal in the Kerberos database, <command>kinit</command> issues an error message. If that happens, supply <command>kinit</command> with the name of the correct principal as an argument on the command line (<command>kinit <replaceable>&lt;principal&gt;</replaceable></command>).
> 					</para>
> 				</note>
> 			</step>
>@@ -571,7 +571,7 @@ Entry for principal host/slavekdc.example.com with kvno 3, encryption type DES c
> 		<para>
> 			Now perform a manual database propagation test by dumping the realm database, on the master KDC, to the default data file which the <command>kprop</command> command will read (<filename>/var/kerberos/krb5kdc/slave_datatrans</filename>), and then use the <command>kprop</command> command to transmit its contents to the slave KDC.
> 		</para>
>-<literallayout>		<computeroutput><prompt>#</prompt> <userinput>/usr/kerberos/sbin/kdb5_util dump /var/kerberos/krb5kdc/slave_datatrans</userinput><prompt>#</prompt> <userinput>kprop slavekdc.example.com</userinput></computeroutput>		
>+<literallayout>		<computeroutput><prompt>#</prompt> <userinput>/usr/sbin/kdb5_util dump /var/kerberos/krb5kdc/slave_datatrans</userinput><prompt>#</prompt> <userinput>kprop slavekdc.example.com</userinput></computeroutput>		
> </literallayout>
> 		<para>
> 			Using <command>kinit</command>, verify that a client system whose <filename>krb5.conf</filename> lists only the slave KDC in its list of KDCs for your realm is now correctly able to obtain initial credentials from the slave KDC.
>-- 
>1.7.1
>

Actions: View | Diff

Attachments on bug 907200: 692937