password change protocol implementation

[Ken Raeburn]

Ken Hornstein <kenh at cmf.nrl.navy.mil> writes:
> Hm.  That seems like a good idea ... but how do you want to implement
> it, since chpw is in the admin server and is seperate from the KDC?
> Do you want to have the kadmin server Makefile reach over and compile
> network.c from the KDC directory?

We've got a few files being used in multiple places already.  We're
kind of schizophrenic about how we deal with it.  I think we're:

 - copying source files from other directories (daemon.c)
 - pulling object files from other directories (profile code)
 - building static libraries not installed (ss)
 - include a "header" file with significant code (fake-addrinfo.h)

In this case, for the short term, I'd be okay with copying the source
file over, but in the longer term, a static library for server process
support code (socket management, logging, anything else? maybe some
kdb code, maybe the one-shot listener code we use for some application
servers during testing?) is probably a better idea.  If you feel like
starting that library with just this one source file, that's okay too.

Ken