Ticket History #796: NASA use of MIT Kerberos?

# Mon Aug 19 14:14:02 2002 The RT System itself - Default: Import/ changed from (no value) to (no value)

Download (untitled) / with headers
text/plain 3.3KiB

From william.baker@lmco.com Thu Dec 23 16:29:22 1999
Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by rt-11.MIT.EDU (8.7.5/8.7.3) with SMTP id QAA05367 for <bugs@RT-11.MIT.EDU>; Thu, 23 Dec 1999 16:29:17 -0500
Received: from mailgw1a.lmco.com by MIT.EDU with SMTP
id AA10299; Thu, 23 Dec 99 16:29:05 EST
Received: from emss02g01.ems.lmco.com (emss02g01.ems.lmco.com [198.7.15.39])
by mailgw1a.lmco.com (8.8.8/8.8.8) with ESMTP id OAA06248
for <krb5-bugs@mit.edu>; Thu, 23 Dec 1999 14:29:14 -0700 (MST)
Received: from CONVERSION-DAEMON by lmco.com (PMDF V5.2-32 #38887) id <0FN700C01QCOAS@lmco.com> for krb5-bugs@mit.edu; Thu,
23 Dec 1999 14:29:12 -0700 (MST)
Received: from emss02i01.ems.lmco.com ([198.7.15.35]) by lmco.com (PMDF V5.2-32 #38887)
with ESMTP id <0FN700NORQCLHA@lmco.com> for krb5-bugs@mit.edu; Thu, 23 Dec 1999 14:29:09 -0700 (MST)
Received: by emss02i01.ems.lmco.com with Internet Mail Service (5.5.2448.0) id <Z3FBDKB0>; Thu, 23 Dec 1999 14:30:17 -0700
Message-Id: <59D51330D936D2119F250000F8046412039F1390@EMSS02M17.ems.lmco.com>
Date: Thu, 23 Dec 1999 14:29:09 -0700
From: "Baker, William" <william.baker@lmco.com>
To: "'MIT Kerberos Bugs'" <krb5-bugs@MIT.EDU>
Subject: NASA use of MIT Kerberos?

Show quoted text

>Number: 796
>Category: pending
>Synopsis: NASA use of MIT Kerberos?
>Confidential: yes
>Severity: serious
>Priority: medium
>Responsible: gnats-admin
>State: closed
>Class: sw-bug
>Submitter-Id: unknown
>Arrival-Date: Thu Dec 23 16:30:00 EST 1999
>Last-Modified: Thu Apr 4 17:22:52 EST 2002
>Originator: "Baker, William" <william.baker@lmco.com>
>Organization:
>Release:
>Environment:
>Description:

Request for information...

1. We are using at NASA/JSC version 5, release 1.0 of Kerberos,
compiled for OSF Version 4.0D.
2. We were previously using a version of Kerberos sold by Digital
Equipment Corporation.
3. In using the new MIT version we have noticed some differences.
a. During build of the principal database, and extract
operations on the principal database, the krb5 KDC daemon disconnects from
the database.
b. During srvtab extraction from the database, the size of the
principal database grows, and seems to contain new information. This causes
old srvtab files to not be in synch with the principal database.
4. We are using kadmin.local now in place of the DEC kdb5_edit utility
for the build of the principal database, and the extraction of the srvtab
files.
5. We are using the "glob" function under kadmin.local to extract large
groups of principals for the srvtab files.

We would appreciate some insite into why the KDC daemon disconnects from the
principal database, and its impact on real-time kerberos database queries,
We would like to understand why the extraction process causes the principal
database to grow, and why it results in old srvtab files no longer being
usable. Any possible workarounds for the srvtab and KDC problems would be
appreciated. A general explanation of how these systems work together, with
respect to kadmin.local, and any specifics regarding the items 1-4 listed
above would be helpful.

Bill Baker
Email ID: Baker, William
SMTP: william.baker@lmco.com
Lockheed-Martin, CSOC Contract.

Show quoted text

>How-To-Repeat:
>Fix:
>Audit-Trail:

State-Changed-From-To: open-closed
State-Changed-By: hartmans
State-Changed-When: Thu Apr 4 17:22:49 2002
State-Changed-Why:

Show quoted text

>Unformatted:

# Mon Aug 19 14:14:02 2002 The RT System itself - Component pending added

# Tue Mar 11 16:57:46 2003 tlyu (Taylor Yu) - Subject changed from 'NASA use of MIT Kerberos? ' to 'NASA use of MIT Kerberos?'

# Tue Mar 11 16:57:46 2003 tlyu (Taylor Yu) - Tags nochange added