[3] in Kerberos_V5_Development

home help back first fref pref prev next nref lref last post

Comments/questions on library interface

jtkohl@ATHENA.MIT.EDU (jtkohl@ATHENA.MIT.EDU)
Mon Dec 4 15:08:12 1989

Date: Tue, 21 Nov 89 15:34:37 -0500
From: John T Kohl <jtkohl@ATHENA.MIT.EDU>
To: sommerfeld@APOLLO.COM
In-Reply-To: Bill Sommerfeld's message of Tue, 21 Nov 89 14:16:27 EST,
	<8911211915.AA25293@xuucp.ch.apollo.com>
Subject: Re: Comments/questions on library interface.

> Date: Tue, 21 Nov 89 14:16:27 EST
> From: sommerfeld@APOLLO.COM (Bill Sommerfeld)

> What's wrong with "krb_"? 

I've actually started using krb5, which sounds better, and avoids
conflicts with v4 stuff.

>    > I would suggest using an "encryption object" containing a key and
>    > pointers to encrypt/decrypt functions 

>    I like this idea; it makes things like keeping a key schedule around
>    much easier.

> On second thought, it should be "a key, a pointer to a vector of
> encrypt/decrypt functions, and whatever other stuff is needed"; the
> vector can be shared and read-only like a C++ virtual function table..

Look around (in your spare time :-) at stuff in
/mit/kerberos/v5src/include/*.h; this is where I'm starting to play with
include files.

> One other question:  is there any schedule for implementing all this
> at Athena?

We are planning to spring some watchmakers on it in January; I don't
know how far we'll get by the end.

Enjoy the weekend!

John

home help back first fref pref prev next nref lref last post