Skip Menu |

Download (untitled) / with headers
text/plain 3.5KiB
From Thu Oct 24 12:59:14 1996
Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU []) by rt-11.MIT.EDU (8.7.5/8.7.3) with SMTP id MAA25443 for <bugs@RT-11.MIT.EDU>; Thu, 24 Oct 1996 12:59:13 -0400
Received: from PO10.ANDREW.CMU.EDU by MIT.EDU with SMTP
id AA00881; Thu, 24 Oct 96 12:59:08 EDT
Received: (from postman@localhost) by (8.8.2/8.8.0) id MAA00855 for; Thu, 24 Oct 1996 12:58:52 -0400
Received: via switchmail; Thu, 24 Oct 1996 12:58:50 -0400 (EDT)
Received: from via qmail
ID </afs/>;
Thu, 24 Oct 1996 12:58:28 -0400 (EDT)
Received: from via qmail
ID </afs/>;
Thu, 24 Oct 1996 12:58:26 -0400 (EDT)
Received: from
Thu, 24 Oct 1996 12:58:24 -0400 (EDT)
Message-Id: <>
Date: Thu, 24 Oct 1996 12:58:24 -0400 (EDT)
From: John Gardiner Myers <jgm@CMU.EDU>
To: krb5-bugs@MIT.EDU
Subject: krb5-beta7: Bad failure mode parsing kdc.conf

Show quoted text
>Number: 134
>Category: pending
>Synopsis: krb5-beta7: Bad failure mode parsing kdc.conf
>Confidential: yes
>Severity: serious
>Priority: medium
>Responsible: gnats-admin
>State: closed
>Class: sw-bug
>Submitter-Id: unknown
>Arrival-Date: Thu Oct e 13:00:01 EDT 1996
>Last-Modified: Thu Dec 05 18:53:01 EST 1996

State-Changed-From-To: open-closed
State-Changed-By: hartmans
State-Changed-When: Fri Nov 1 18:38:55 1996

This problem certainly exists, but it is a duplicate of krb5-libs/69
in our database.

From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: John Gardiner Myers <jgm@CMU.EDU>
Cc: krb5-bugs@MIT.EDU
Subject: Re: pending/134: krb5-beta7: Bad failure mode parsing kdc.conf
Date: Thu, 14 Nov 1996 14:55:50 -0500

The bug you reported has been fixed for the 1.0 release; if the
kdc.conf file has syntax errors, programs which try to read it will
abort with an error.

- Ted
Show quoted text
I had extra garbage in my kdc.conf file:

------------------------------begin kdc.conf file
kdc_ports = 88,750

profile = /etc/krb5.conf
database_name = /var/krb5kdc/principal
admin_database_name = /var/krb5kdc/principal.kadm5
admin_database_lockfile =
admin_keytab = /var/krb5kdc/kadm5.keytab
acl_file = /var/krb5kdc/kadm5.acl
dict_file = /var/krb5kdc/kadm5.dict
key_stash_file = /var/krb5kdc/.k5.PORTOLACOMM.COM
kadmind_port = 749
max_life = 10h 0m 0s
max_renewable_life = 7d 0h 0m 0s
master_key_type = des-cbc-crc
supported_enctypes = des-cbc-crc:normal des-cbc-crc:v4
cd /var
------------------------------ end kdc.conf file

(with the mkdir line not ending with a LF)

Trying to run krb5kdc, the behavior was not a printed error message as
one would expect. Instead krb5kdc silently ignored all the settings
for the PORTOLACOMM.COM domain, instead picking the compiled-in

I spent quite a few minutes running gdb on krb5kdc trying to track
this down. The code really needs to have better error dectection and
diagnostics for stuff like this.

_.John Gardiner Myers Internet: jgm+@CMU.EDU
LoseNet: ...!seismo!ihnp4!!give!up