From owner-freebsd-questions Mon Oct 15 18:57:30 2001 Delivered-To: freebsd-questions@freebsd.org Received: from stjohn.stjohn.ac.th (stjohn.stjohn.ac.th [202.21.144.1]) by hub.freebsd.org (Postfix) with ESMTP id 8B08437B409 for ; Mon, 15 Oct 2001 18:57:25 -0700 (PDT) Received: from tulip ([203.151.134.104]) by stjohn.stjohn.ac.th (8.9.3+Sun/8.9.3) with SMTP id IAA24211; Tue, 16 Oct 2001 08:56:20 +0700 (ICT) Message-Id: <3.0.6.32.20011016085640.007d34f0@stjohn.stjohn.ac.th> X-Sender: mcrogerm@stjohn.stjohn.ac.th X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Tue, 16 Oct 2001 08:56:40 +0700 To: cjclark@alum.mit.edu From: Roger Merritt Subject: Re: Can't get PuTTY to connect Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: <20011015131543.A293@blossom.cjclark.org> References: <3.0.6.32.20011015182409.007b6960@stjohn.stjohn.ac.th> <3.0.6.32.20011015170134.007b0100@stjohn.stjohn.ac.th> <3.0.6.32.20011015170134.007b0100@stjohn.stjohn.ac.th> <20011015033737.Q309@blossom.cjclark.org> <3.0.6.32.20011015182409.007b6960@stjohn.stjohn.ac.th> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 01:15 PM 10/15/01 -0700, you wrote: >On Mon, Oct 15, 2001 at 06:24:09PM +0700, Roger Merritt wrote: > >[snip] > >> Turned out sshd wasn't running. I had to configure it and create keyfiles >> in /etc/ssh. I hadn't checked before because it was running by default >> under 4.3-STABLE and I forgot that 4.4-STABLE has upgraded to OpenSSH 2.9 >> so sshd is not started by default. > >sshd(8) runs by default in the same manner in 4.4-STABLE. > ??? Two things. /etc/defaults/rc.conf has 'sshd_enable="NO", which has to be changed in /etc/rc.conf, and the daemon won't run unless you have the appropriate key files in /etc/ssh, which I didn't. >[snip] > >> Right. It turns out it's not a FreeBSD issue at all (unless running PuTTY >> is so much a part of running FreeBSD that it's become part of the overall >> system). I'm now able to connect, but PuTTY reports it can't load my public >> key. > >If you are logging FROM the PuTTY machine INTO the FreeBSD machine, >PuTTY needs a private key, not a public key. Yes, that's why I said it's not a FreeBSD issue. For some reason PuTTY can't read the public key file I generated with ssh-keygen on my FreeBSD box. At the same time, the key generated by puttygen.exe isn't accepted by sshd. Examining the files, the FreeBSD-generated key is all printable characters, while the file generated by puttygen.exe is all non-printable. I don't understand what's going on and have sent a query to the PuTTY web site, but it seems like this should be a common problem. Do most people run PuTTY in telnet mode? >-- >Crist J. Clark | cjclark@alum.mit.edu > | cjclark@jhu.edu >http://people.freebsd.org/~cjc/ | cjc@freebsd.org > -- Roger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message