[1190] in Kerberos_V5_Development
Re: [eichin@kitten.gen.ma.us (Mark W. Eichin)] v5 rcp doesn't support v4 rcp -x...
daemon@ATHENA.MIT.EDU (Sam Hartman)
Thu May 16 00:19:23 1996
To: Ken Raeburn <raeburn@cygnus.com>
Cc: krbdev@MIT.EDU
From: Sam Hartman <hartmans@MIT.EDU>
Date: 16 May 1996 00:19:06 -0400
In-Reply-To: Ken Raeburn's message of 14 May 1996 18:52:37 -0400
>>>>> "Ken" == Ken Raeburn <raeburn@cygnus.com> writes:
Ken> Is this by design? Can we be compatible with v4 somehow?
I don't know. I suspect it would be mildly ugly to support
the V4 compatability, because rcp would then have to be set-uid, which
it doesn't currently need. I.E. you would have to re-verify the
correct operation of the server code when run as root. I think a
better solution would be to allow krb4 rcp to be run by kshd. This
may not actually work if krb4 has an rcp that expects to be able to
write to stdout.
You know, I guess we could use socketpair instead of pipe in
kshd.c and then kshd would work in encrypting mode with all rcps. I
am not sure what other bugs this introduces, but it is somethign to
consider.
