Skip Menu |

Subject: Implement new key storage architecture
Date: Fri, 20 Sep 2002 14:40:54 -0400 (EDT)
From: (Sam Hartman)

During the 1.2.3 crypto transition we added code to coerce the enctype
to be what was expected by calling routines and attached the following
* Coerce the enctype of the output keyblock in case we got an
* inexact match on the enctype; this behavior will go away when
* the key storage architecture gets redesigned for 1.3.

Do we still want to do this for 1.3?
Presume not, but I'm opening this ticket for discussion.
Subject: CVS Commit
Change comments to remove the note that we're going to redesign key
storage architecture for 1.3.

To generate a diff of this commit:

cvs diff -r5.145 -r5.146 krb5/src/lib/kdb/ChangeLog
cvs diff -r5.14 -r5.15 krb5/src/lib/kdb/keytab.c
cvs diff -r5.55 -r5.56 krb5/src/lib/krb5/keytab/ChangeLog
cvs diff -r5.5 -r5.6 krb5/src/lib/krb5/keytab/kt_file.c