This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours
Bug 78202 - /etc/init.d/krb5kdc checks for hard coded file name
/etc/init.d/krb5kdc checks for hard coded file name
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: krb5 (Show other bugs)
8.0
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-11-19 18:53 EST by Jim Richardson
Modified: 2007-04-18 12:48 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-08-08 11:46:40 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Jim Richardson 2002-11-19 18:53:00 EST
From Bugzilla Helper:
User-Agent: Opera/6.1 (Linux 2.4.18-18.8.0 i686; U)  [en]

Description of problem:
I followed the documented kerberos setup and created my database with a name that wasn't "prinicle". The init.d script checks for the existence of the "principle" file and exits if it doesn't exist. I simply touched a principle file in the correct location and the server seems to be working fine. Of course I am not sure YET how to verify that, since it is my first time to set it up. 

The kadmin script has the same issue.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Setup a new kerberos database named something besides "principle"
2.
3.
	

Actual Results:  The server silently refuses to start

Expected Results:  Expected it to at least error with a message if a sanity test failed. But it will need to be improved to awk out the principle(s) names and verify that at least one exsits. As I read the documentaion there could be more than one princilple database running on a system.

Additional info:
Comment 1 Bill Nottingham 2006-08-07 14:27:05 EDT
Red Hat Linux is no longer supported by Red Hat, Inc. If you are still
running Red Hat Linux, you are strongly advised to upgrade to a
current Fedora Core release or Red Hat Enterprise Linux or comparable.
Some information on which option may be right for you is available at
http://www.redhat.com/rhel/migrate/redhatlinux/.

Red Hat apologizes that these issues have not been resolved yet. We do
want to make sure that no important bugs slip through the cracks.
Please check if this issue is still present in a current Fedora Core
release. If so, please change the product and version to match, and
check the box indicating that the requested information has been
provided. Note that any bug still open against Red Hat Linux on will be
closed as 'CANTFIX' on September 30, 2006. Thanks again for your help.
Comment 2 Jim Richardson 2006-08-08 11:46:40 EDT
Well it is good to know that after all these years that have passed this bug 
report wasn't closed. I suppose ignoring issues until a product expires is 
better than just sweeping them under the rug. Regardless, I've long since 
given up on krb as I now try to adhere to the KISS principle.

Note You need to log in before you can comment on or make changes to this bug.