Ticket History #1193: Implement new key storage architecture

# Fri Sep 20 14:40:55 2002 hartmans (Sam Hartman) - Ticket created

To:	rt-krb5@krbdev.mit.edu
Subject:	Implement new key storage architecture
Date:	Fri, 20 Sep 2002 14:40:54 -0400 (EDT)
From:	hartmans@mit.edu (Sam Hartman)

Download (untitled) / with headers
text/plain 461B

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.
*/
legend.

Do we still want to do this for 1.3?
Presume not, but I'm opening this ticket for discussion.

# Fri Sep 20 14:41:24 2002 hartmans (Sam Hartman) - Target_Version 1.3 added

# Fri Sep 20 14:41:25 2002 hartmans (Sam Hartman) - Given to tlyu (Taylor Yu)

# Sat Feb 08 03:12:51 2003 tlyu (Taylor Yu) - Status changed from 'new' to 'resolved'

# Sat Feb 08 03:12:51 2003 tlyu (Taylor Yu) - Correspondence added

From:	tlyu@mit.edu
Subject:	CVS Commit

Download (untitled) / with headers
text/plain 357B

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

# Wed Mar 12 20:53:53 2003 tlyu (Taylor Yu) - Version_Fixed 1.3 added