Date: Tue, 16 Oct 2001 10:36:25 +0700 From: Roger Merritt <mcrogerm@stjohn.ac.th> To: cjclark@alum.mit.edu Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Can't get PuTTY to connect Message-ID: <3.0.6.32.20011016103625.007b5320@stjohn.stjohn.ac.th> In-Reply-To: <20011015192946.D293@blossom.cjclark.org> References: <3.0.6.32.20011016085640.007d34f0@stjohn.stjohn.ac.th> <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> <20011015131543.A293@blossom.cjclark.org> <3.0.6.32.20011016085640.007d34f0@stjohn.stjohn.ac.th>
next in thread | previous in thread | raw e-mail | index | archive | help
At 07:29 PM 10/15/01 -0700, you wrote: >On Tue, Oct 16, 2001 at 08:56:40AM +0700, Roger Merritt wrote: >> 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. > >That line has been in /etc/defaults/rc.conf since Feburary 24, >2000. If the keys do not exist in /etc/ssh, the rc.network script will >create them. > Then I don't know what happened. sshd *was* running when I was still running 4.3-STABLE and wasn't yesterday. And I don't understand -- if the default line is 'sshd_enable="NO"', how can sshd be running by default? >> >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 > ^^^^^^^^^^^^^^^ >If you are logging in FROM PuTTY, you need the _private_ key on that >machine. > Aha! >> 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, > >The public key is, the private key is not. > OK, that's where *that* problem was. PuTTY now connects the way I thought it should. >> 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? > >Nope. A lot of people just use passwords though. I personally never >used RSA keys with PuTTY, but I did use them with TeraTerm and the SSH >extensions to it. No problems between TeraTerm SSH and OpenSSH. I >prefered TeraTerm SSH at the time since it did X11 forwarding. Well, I also downloaded TeraTerm and now that I understand the process I may give it a try. I seem to recall I tried it several years ago as a regular telnet replacement and didn't care for its appearance so went to NetTerm. Hmmm. Maybe I also downloaded Secure NetTerm. Thanks very much for taking the time to help me out. Looking back over my postings I'm embarrassed at sounding so dense -- you would think I would have learned more about problem-solving by now. But I'm really grateful to people like you who are willing to spend time helping others. >-- >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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.6.32.20011016103625.007b5320>