Received: from SOUTH-STATION-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA01393; Fri, 15 Mar 96 01:35:22 EST
Received: from cygnus.com by MIT.EDU with SMTP
	id AA26147; Fri, 15 Mar 96 01:34:36 EST
Received: from tweedledumb.cygnus.com (tweedledumb.cygnus.com [192.80.44.1]) by cygnus.com (8.6.12/8.6.9) with SMTP id WAA07309; Thu, 14 Mar 1996 22:35:18 -0800
Received: from scuba.cygnus.com by tweedledumb.cygnus.com (4.1/4.7) id AA23261; Fri, 15 Mar 96 01:34:01 EST
Message-Id: <9603150634.AA23261@tweedledumb.cygnus.com>
Received: by scuba.cygnus.com
	(1.39.111.2/16.2) id AA294501760; Fri, 15 Mar 1996 01:36:00 -0500
Date: Fri, 15 Mar 1996 01:36:00 -0500
From: "Mark W. Eichin" <eichin@cygnus.com>
To: proven@cygnus.com
Cc: nlgilman@cygnus.com
In-Reply-To: <9603150442.AA20335@tweedledumb.cygnus.com> (nlgilman@cygnus.com)
Subject: Re: what to start on

1) you're in /.klogin and /etc/passwd on scuba. In group cygnus by
default; as yourself you should be able to create a directory in
/scuba/home/build/ for workspace.
2) you're in /.klogin on tito. also changed your group to 1002/cygnus.
3) /.klogin on tweedledumber, also changed your group to 1002/cygnus.

>> One of the bugs we need to test is whether or not rsh -f works and
>> whether or not rcp -x works at all.

To do this, install cns5 on tito and dumber. /9h/eichin/parc/96q2 has
sparc-sunos build tree; you should be able to do a make install DESTDIR=...
to get stuff to install. /9h/cns5 is where the binaries should go;
look at how stuff is set up now. (/usr/cygnus/cns5-96q1 will be the
place they get installed; just move stuff that's there now, and don't
lose the lib/krbkdc directory - feel free to start a new kdc using it
though.)

/scuba/home/build/eichin/v5/cust has a solaris build tree; same bit
with make install, for dumber.

tito and dumber already have working /etc/v5srvtab files; if the
format is changed such that you need to extract new ones, *tell me*
because we'll have to educate the customers but go ahead and extract
new ones from the database on tito.

Preferably use a different port for v5rsh on these machines, as people
are still using the v4 services and need to get work done on them. Be
careful with them :-)

Your Mission is to determine:
	if rsh -f now forwards tickets at all. 
	if rsh -f -x works as well.
	if rcp -x now works at all (it shouldn't forward tickets any
more, unless I'm confused about sam's changes...)

After you get those answers, should double check that
	v5 rlogin 
		- works
		- works with -x
		- works with -f
		- works with -f -x
	same with telnet.
Double check the -f/-F difference as well, in all cases.


> This will involve setting up a real for testing.  Tito and dummer are

Actually, don't set up a new realm -- they've got CYGNUS.COM keys
already, that should be enough for the test. If it doesn't work at all
(ie. normal rsh doesn't even work) you might consider setting up a
realm with new keys [all the existing ones are converted v4 keys,
after all] but likewise I need to know to explain to the customers...
