[7600] in Athena Bugs
[daemon@ATHENA.MIT.EDU : [mukund: kdb_verify_master_key]]
daemon@ATHENA.MIT.EDU (Jonathan I. Kamens)
Wed May 29 19:27:50 1991
Date: Wed, 29 May 91 19:27:39 -0400
From: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
To: bugs@ATHENA.MIT.EDU
------- Forwarded transaction
[0617] daemon@ATHENA.MIT.EDU (Theodore Ts'o) Kerberos_Bugs 05/28/91 22:36 (51 lines)
Subject: [mukund: kdb_verify_master_key]
Date: Tue, 28 May 91 22:35:58 -0400
From: tytso@ATHENA.MIT.EDU (Theodore Ts'o)
To: kerberos-bugs@ATHENA.MIT.EDU
Reply-To: tytso@ATHENA.MIT.EDU
------- Forwarded Message
Date: 28 May 91 16:25:55 GMT
From: tivoli!mukund@shelby.Stanford.EDU (mukund)
Organization: Tivoli Systems Inc., Austin, TX
Subject: kdb_verify_master_key
Sender: owner-comp-protocols-kerberos@shelby.Stanford.EDU
To: kerberos@shelby.Stanford.EDU
In Version 4 : admin/kdb_edit.c
kdb_verify_master_key(master_key, master_key_schedule, stdout)
static C_Block master_key;
static Key_schedule master_key_schedule;
FILE *stdout;
Now change the last argument to (FILE *)NULL ,and even if the
master password does not verify, the routine returns the master
key version (> 1) and all is well.
The problem seems to be in the following bit of code
in kdb_verify_master_key(..)
>if (n && (out != (FILE *) NULL)) {
> fprintf(out, gettxt("\n\07\07verify_master_key: Invalid master key;
> does not match database.\n"));
> return (-1);
> }
Comments ???
I have seen some wierd stuff in version 4 but this takes the cake.
---Mukund
__________________________________________________________
Mukund Belliappa mukund@tivoli.com
Tivoli systems Inc.
Austin Texas.
(512)794-9070
------- End Forwarded Message
--[0617]--
------- End forwarded transaction
