From owner-freebsd-stable Thu Mar 9 7:34: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D07B537B57A; Thu, 9 Mar 2000 07:33:55 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id CAA66967; Thu, 9 Mar 2000 02:16:36 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id CAA08113; Thu, 9 Mar 2000 02:16:20 -0700 (MST) Message-Id: <200003090916.CAA08113@harmony.village.org> To: Matt Heckaman Subject: Re: ssh1 + openssh 1.2.2 + tcsh 6.09.00 Cc: Kris Kennaway , FreeBSD-STABLE In-reply-to: Your message of "Wed, 08 Mar 2000 23:01:57 EST." References: Date: Thu, 09 Mar 2000 02:16:20 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Matt Heckaman writes: : 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.. The bug is *NOT* with tcsh. It works great. I've been using it plus ssh and openssh for years. I've used lots of different versions, including this one and have seen no problems. Most likely this is the classic bug of having your .cshrc and/or .login produce output when prompt isn't defined. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message