From owner-freebsd-current Fri Apr 21 14:16:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id ED26D37BA8F; Fri, 21 Apr 2000 14:16:52 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA40009; Fri, 21 Apr 2000 14:16:52 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 21 Apr 2000 14:16:52 -0700 (PDT) From: Kris Kennaway To: Archie Cobbs Cc: Mike Pritchard , kris@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: ssh to freefall broken In-Reply-To: <200004211739.KAA03491@bubba.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 21 Apr 2000, Archie Cobbs wrote: > This only happens when going from machine A -> machine B -> freefall. > Machine A is 3.4-REL, machine B is either 4.0-stable or 5.0-current > (as of a couple of days ago). Hmm. It works for me going 5.0-C -> 5.0-C -> freefall using openssh both times. Perhaps it's some bug in the ssh->openssh agent forwarding..I'll see if I can get it to fail with ssh. I noticed that you're running an old version of ssh, too, which may have some security problems (the 1.2.27 upgrade fixed some discovered problems, but I forget what they were). > It also may have to do with the warning 'Server lies about size of > server host key: actual size is 1023 bits vs. announced 1024.' That should be harmless. 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-current" in the body of the message