[2073] in Kerberos-V5-bugs

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

Re: possible rsh/kshd problem?

daemon@ATHENA.MIT.EDU (Dave McGuire)
Thu Jul 4 03:23:38 1996

Date: Thu, 4 Jul 1996 03:01:51 -0400
From: Dave McGuire <mcguire@rocinante.digex.net>
To: Ken Raeburn <raeburn@cygnus.com>
Cc: "Richard Basch" <basch@lehman.com>, Mark Eichin <eichin@cygnus.com>,
        Sam Hartman <hartmans@MIT.EDU>, kerberos@MIT.EDU, krb5-bugs@MIT.EDU,
        rdist-bugs@usc.edu
In-Reply-To: Re: possible rsh/kshd problem? (Ken Raeburn)

On July 3, you wrote:
> "Richard Basch" <basch@lehman.com> writes:
> > Actually, if appl/rdist had been based on a more recent rdist source
> > distribution, it would not have had the problem.  We ran into the same
> > problem at Lehman with our modified rdist, and we simply started
> > integrating our changes into a more recent version.
> 
> It was current when I merged it into our Kerberos v4 tree a while
> back.  I've taken 6.1.2 and partially "autoconfiscated" it, but I'm
> not done yet, and the rdist developers seemed less than psyched about
> it, so it's been low on my priority list.

  As it turns out, the problem does indeed exist in rdist 6.1.2, and
the patch does not solve the problem.  One hunk even got rejected
(from rdistd.c, "rem" is now separated into "rem_w" and  "rem_r") but
it looks like the code should now treat the fd's properly...it must be
something else.

  I will try to dig into the code a bit tomorrow after I've had some
sleep.  I'll send mail if I find anything.


                            -Dave McGuire
                             mcguire@digex.net

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