From owner-freebsd-stable Wed Mar 8 19:55:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 79D2537B532; Wed, 8 Mar 2000 19:55:30 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id TAA78726; Wed, 8 Mar 2000 19:55:30 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 8 Mar 2000 19:55:30 -0800 (PST) From: Kris Kennaway To: Matt Heckaman Cc: FreeBSD-STABLE Subject: Re: ssh1 + openssh 1.2.2 + tcsh 6.09.00 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message