Testing for V4 compatibility in CNS V5.
=======================================

The dejagnu test harness makes it possible to test all programs that
we could test by hand. The time taken to test something by hand *once*
is comparable to the time needed to add that one test to the test
suite so it can be run forever.

The broad claim that these tests support is that
* CNS V5 is backwards compatible with CNS V4.
This claim breaks down into the following major components:
	* V4 basic clients can talk to V5 servers.
In particular, the clients
		* kinit, ksrvtgt (kdc) [done]
		* kpasswd (v4kadmind)
		* get_srvtab (v4kadmind)
		* ksu (local host)
		* ksrvutil (kdc, v4kadmind)
		* kadmin (v4kadmind) [may not be supported]
	* V4 application clients can talk to V5 application servers.
		* ftp (gssftpd) [may not be supported]
		* krdist (kshd, rdistd)
		* movemail (popper) [may not be supported]
		* rlogin (klogind)
		* rsh (kshd)
		* rcp (kshd, rcp server)
		* telnet (telnetd)
		* tftp -- dropped (not supported in v4 either)
	* V4 key databases can be loaded into V5 key databases.
		* we can provide a slave dump and test it
		* we can use kdb_init/kdb_edit to generate one	
		* we verify the keys against at least
			* kinit
			* ksrvtgt
	* V5 key databases can be loaded into V4 key databases.
		* within certain rules about key generation/salttypes
	* V4 application servers can be run with keys pulled from V5 databases.
		* ie, kadmin xst4 and kdb5_edit xst4 actually work with...
		* ksrvtgt
		* ftpd
		* kprop/kpropd?
		* klogind
		* kshd
		* popper
		* telnetd
		* tftpd -- not supported in v4 anyway





Local Variables:
mode: outline
outline-regexp: "[	]*\\* "
End:
