From owner-freebsd-security Wed Mar 6 8:18:22 2002 Delivered-To: freebsd-security@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id DEE6D37B416 for ; Wed, 6 Mar 2002 08:18:10 -0800 (PST) Received: (from david@localhost) by bunrab.catwhisker.org (8.11.6/8.11.6) id g26GI8N20045; Wed, 6 Mar 2002 08:18:08 -0800 (PST) (envelope-from david) Date: Wed, 6 Mar 2002 08:18:08 -0800 (PST) From: David Wolfskill Message-Id: <200203061618.g26GI8N20045@bunrab.catwhisker.org> To: mwlucas@blackhelicopters.org, setantae@submonkey.net Subject: Re: ssh keys not working? Cc: security@FreeBSD.ORG In-Reply-To: <20020306161335.GC57440@submonkey.net> Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Date: Wed, 6 Mar 2002 16:13:35 +0000 >From: Ceri >Other than that, check that your Protocol line is 1,2 instead of 2,1. I would be somewhat surprised if that were effective, as I have Protocol 2,1 explicitly in my ~/.ssh/ssh_config, and relay on ssh for connecting to other machines routinely. Use of "-v" when invoking ssh can often help spot the problem. Cheers, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill david@catwhisker.org I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message