From hartmans@MIT.EDU Thu Nov 14 17:57:31 1996
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 RAA11765 for <bugs@RT-11.MIT.EDU>; Thu, 14 Nov 1996 17:57:31 -0500
Received: from PORTNOY.MIT.EDU by MIT.EDU with SMTP
id AA18304; Thu, 14 Nov 96 17:57:30 EST
Received: by portnoy.MIT.EDU (5.x/4.7) id AA19533; Thu, 14 Nov 1996 17:57:29 -0500
Message-Id: <9611142257.AA19533@portnoy.MIT.EDU>
Date: Thu, 14 Nov 1996 17:57:29 -0500
From: hartmans@MIT.EDU
Reply-To: hartmans@MIT.EDU
To: krb5-bugs@MIT.EDU
Subject: Provide mechanism for changing database master key
X-Send-Pr-Version: 3.99
X-GNATS-Notify: hartmans@mit.edu,roma@uiuc.edu
System: SunOS portnoy 5.4 Generic_101945-37 sun4m sparc
As a somewhat related note, we may consider removing the
requirement from the docs that humans are expected to know or remember
the master key
From: "Barry Jaspan" <bjaspan@MIT.EDU>
To: hartmans@MIT.EDU
Cc: krb5-bugs@MIT.EDU
Subject: Re: krb5-admin/192: Provide mechanism for changing database master key
Date: Fri, 15 Nov 1996 14:13:10 -0500
IMHO, this feature logically belongs in kdb5_util. I think it was
previously implemented (in kdb5_edit) as part of load_db.
Responsible-Changed-From-To: bjaspan->krb5-unassigned
Responsible-Changed-By: mdh
Responsible-Changed-When: Wed Jun 24 00:49:51 1998
Responsible-Changed-Why:
bjaspan is no longer with the kerberos team
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 RAA11765 for <bugs@RT-11.MIT.EDU>; Thu, 14 Nov 1996 17:57:31 -0500
Received: from PORTNOY.MIT.EDU by MIT.EDU with SMTP
id AA18304; Thu, 14 Nov 96 17:57:30 EST
Received: by portnoy.MIT.EDU (5.x/4.7) id AA19533; Thu, 14 Nov 1996 17:57:29 -0500
Message-Id: <9611142257.AA19533@portnoy.MIT.EDU>
Date: Thu, 14 Nov 1996 17:57:29 -0500
From: hartmans@MIT.EDU
Reply-To: hartmans@MIT.EDU
To: krb5-bugs@MIT.EDU
Subject: Provide mechanism for changing database master key
X-Send-Pr-Version: 3.99
X-GNATS-Notify: hartmans@mit.edu,roma@uiuc.edu
Show quoted text
>Number: 192
>Category: krb5-admin
>Synopsis: Provide mechanism for changing database master key
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: krb5-unassigned
>State: open
>Class: change-request
>Submitter-Id: unknown
>Arrival-Date: Thu Nov 14 17:58:01 EST 1996
>Last-Modified: Wed Jun 24 00:50:17 EDT 1998
>Originator: Sam Hartman
>Organization:
mit>Category: krb5-admin
>Synopsis: Provide mechanism for changing database master key
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: krb5-unassigned
>State: open
>Class: change-request
>Submitter-Id: unknown
>Arrival-Date: Thu Nov 14 17:58:01 EST 1996
>Last-Modified: Wed Jun 24 00:50:17 EDT 1998
>Originator: Sam Hartman
>Organization:
Show quoted text
>Release: 1.0
>Environment:
>Environment:
System: SunOS portnoy 5.4 Generic_101945-37 sun4m sparc
Show quoted text
>Description:
No mechanism is provided to change the DB master key. This should eventually be fixed.As a somewhat related note, we may consider removing the
requirement from the docs that humans are expected to know or remember
the master key
Show quoted text
>How-To-Repeat:
Show quoted text
>Fix:
Show quoted text
>Audit-Trail:
From: "Barry Jaspan" <bjaspan@MIT.EDU>
To: hartmans@MIT.EDU
Cc: krb5-bugs@MIT.EDU
Subject: Re: krb5-admin/192: Provide mechanism for changing database master key
Date: Fri, 15 Nov 1996 14:13:10 -0500
IMHO, this feature logically belongs in kdb5_util. I think it was
previously implemented (in kdb5_edit) as part of load_db.
Responsible-Changed-From-To: bjaspan->krb5-unassigned
Responsible-Changed-By: mdh
Responsible-Changed-When: Wed Jun 24 00:49:51 1998
Responsible-Changed-Why:
bjaspan is no longer with the kerberos team
Show quoted text
>Unformatted: