Re: more on proff crash building native

[Anders Magnusson <ragge%ludd.ltu.se@localhost>]

Dave McGuire wrote:
> On Feb 14, 2009, at 10:03 PM, der Mouse wrote:
>>> I would suggested that if ssh is the symptom, the problem is tcp.
>>
>> This is highly unlikely; ssh (the protocol) has its own integrity
>> protection, so unless you have turned off MAC checking (or have an
>> implementation that doesn't do it, or has buggy code for it), ssh will
>> normally report an error rather than silently delivering wrong data.
>>
>> sshv2, at least.  I think sshv1 has something similar, but I don't know
>> it well enough to say with any certainty.
>>
>> Especially in view of Brad's report of seeing this on simulated
>> hardware, I think it's far more likely that there's buggy crypto code
>> lurking somewhere.  It might be interesting to try moussh instead of
>> openssh, since it doesn't use the same crypto code; I should dig out
>> one of my desktop VAXen (I think I've got at least one) and see if I
>> can reproduce this.
> 
>   Yebbut...Ragge mentioned problems using CVS as well, suggesting a
> lower-level issue.  Unless he was using SSH as a transport for CVS...?
> 
I use ssh for cvs to checkout the NetBSD source, yes.  That's why I meant
that the problem has been here forever, I have been checking out NetBSD source
forever :-)

Using rsh instead solves the problem.  I use to do that to another machine that
had the ssh tunnel to NetBSD.

-- Ragge