From owner-freebsd-security  Mon Nov  5 12: 9:55 2001
Delivered-To: freebsd-security@freebsd.org
Received: from atkielski.com (atkielski.com [161.58.232.69])
	by hub.freebsd.org (Postfix) with ESMTP id 488DD37B416
	for <freebsd-security@FreeBSD.ORG>; Mon,  5 Nov 2001 12:09:51 -0800 (PST)
Received: from contactdish (ASt-Lambert-101-2-1-14.abo.wanadoo.fr [193.251.59.14]) by atkielski.com (8.11.6) id fA5K9Ew90564; Mon, 5 Nov 2001 21:09:14 +0100 (CET)
Message-ID: <004701c16635$d18a34c0$0a00000a@atkielski.com>
From: "Anthony Atkielski" <anthony@atkielski.com>
To: "Noonan, Mr. Sean P." <noonans@nosc.mil>,
	<freebsd-security@FreeBSD.ORG>
References: <9D20F9E38A32D411AA3C00508B94CCD5066BEF72@REGULUS>
Subject: Re: SecureCRT and SSH2 on FreeBSD
Date: Mon, 5 Nov 2001 21:09:44 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-security.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-security>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-security>
X-Loop: FreeBSD.org

That fixed it!  The sshgen step was missing; I had a vague recollection of doing
something like that before, but I was unable to remember what it was.  Your note
explained what to do.  Thanks.

----- Original Message -----
From: "Noonan, Mr. Sean P." <noonans@nosc.mil>
To: "'Anthony Atkielski'" <anthony@atkielski.com>
Cc: <freebsd-security@FreeBSD.ORG>
Sent: Monday, November 05, 2001 18:51
Subject: RE: SecureCRT and SSH2 on FreeBSD


> I use CRT v3.3 with SSH2 against 4.3-STABLE without problems.  Here's my
> /etc/sshd/sshd_config and the method I use to convert the v2 key for use
> with ssh2.  Any problems email me at my personal address,
> snoonan@snoonan.com.
>
> P.S. - I don't allow root to login directly, but that's not the crux of your
> problem...so it shouldn't matter...
>
> Good luck,
>
> Sean.
>
>
>
> -----Original Message-----
> From: owner-freebsd-security@FreeBSD.ORG
> [mailto:owner-freebsd-security@FreeBSD.ORG]On Behalf Of Anthony
> Atkielski
> Sent: Monday, November 05, 2001 9:14 AM
> To: freebsd-security@FreeBSD.ORG
> Subject: SecureCRT and SSH2 on FreeBSD
>
>
> Can anyone assist me with the exact configuration for getting SecureCRT (on
> Windows) to work with SSH2 against a FreeBSD server?  I got SSH1 to work
> okay,
> and--mysteriously--SSH2 seems to work against my Web server (4.2 release) on
> the
> Net, but I can't connect to my own FreeBSD 4.3 server at home; all I get is
> a
> message saying
>
> Public-key authentication with the SSH2 server for user root failed.  Please
> verify username and public/private key pair.
>
> Do I have to run anything to make SSH2 work, or is sshd sufficient?  I have
> telnetd disabled.  I have PermitRootLogin set to without-password.  root can
> log
> in under SSH1, but nobody can log in under SSH2.
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-security" in the body of the message
>
>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message