Date: Wed, 8 Mar 2000 23:01:57 -0500 From: Matt Heckaman <matt@ARPA.MAIL.NET> To: Kris Kennaway <kris@FreeBSD.org> Cc: FreeBSD-STABLE <stable@FreeBSD.ORG> Subject: Re: ssh1 + openssh 1.2.2 + tcsh 6.09.00 Message-ID: <Pine.BSF.4.21.0003082257500.821-100000@epsilon.lucida.qc.ca> In-Reply-To: <Pine.BSF.4.21.0003081952380.60780-100000@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I completely agree, it most likely is a bug in a tcsh, and I've tried recompiling all things involved. The question is, what does OpenSSH's sshd do differently while recieving a scp from sshv1, that sshd 1.2.27 does not do. I think if we can find tht, we can find what's causing the tcsh problem.. I did not at all mean to imply that OpenSSH was the one that was bugged, simply that the combination was causing problems. I do not have a very good understanding of the internals of openssh & ssh, so I do not know what they would each do differently that could prompt tcsh to die, which is why I wrote in to the list. I've also seen other people report this problem, so I do know it's not me alone - though it's by no means universal, perhaps a combination of certain configurations, or tcshrc/login variables.. I don't know, which is my problem from the start =) Thanks. matt -- Matt Heckaman [matt@arpa.mail.net|matt@relic.net] [Please do not send me] !Powered by FreeBSD/x86! [http://www.freebsd.org] [any SPAM (UCE) e-mail] On Wed, 8 Mar 2000, Kris Kennaway wrote: : Date: Wed, 8 Mar 2000 22:55:30 -0500 : From: Kris Kennaway <kris@FreeBSD.org> : To: Matt Heckaman <matt@ARPA.MAIL.NET> : Cc: FreeBSD-STABLE <stable@FreeBSD.ORG> : Subject: Re: ssh1 + openssh 1.2.2 + tcsh 6.09.00 : : On Wed, 8 Mar 2000, Matt Heckaman wrote: : : > I've heard reports of using scp from ssh 1 to openssh creating problems, : > and I finally now see why - it makes tcsh core! Observe: : : I don't think this is a general problem :) Certainly it does interoperate : very well, perhaps perfectly, with the ssh port. : : Try rebuilding your tcsh port and/or the openssh port. The fact that it's : tcsh dying, not openssh indicates it's a problem with tcsh, possibly a : bug. : : Kris : : ---- : In God we Trust -- all others must submit an X.509 certificate. : -- Charles Forsythe <forsythe@alum.mit.edu> : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0003082257500.821-100000>