From owner-freebsd-questions Mon Nov 27 22:26:37 2000 Delivered-To: freebsd-questions@freebsd.org Received: from bryden.apana.org.au (bryden.apana.org.au [203.3.126.129]) by hub.freebsd.org (Postfix) with ESMTP id B6D9C37B402 for ; Mon, 27 Nov 2000 22:26:27 -0800 (PST) Received: from dougy (dougy.apana.org.au [203.3.126.131]) by bryden.apana.org.au (8.9.3/8.9.3) with ESMTP id QAA21322 for ; Tue, 28 Nov 2000 16:32:13 +1000 (EST) (envelope-from dougy@bryden.apana.org.au) Message-ID: <092401c05905$4ea18290$837e03cb@dougy> From: "Doug Young" To: Subject: SSH setup / RSA keys Date: Tue, 28 Nov 2000 16:34:42 +1000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0921_01C05959.1C090B10" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0921_01C05959.1C090B10 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'm trying to configure SSH login to a 4.2 RELEASE system from various = Windows machines. It certainly appears to be a=20 step forward in securing servers from the moron element that gets its = thrills from wanton vandalism, however as with most=20 new things in unix the documentation quite sparse as far as explaining=20 "exactly_how_do_I_do_this_from_scratch_when_I_ only_first = _stumbled_across_ the beast_an_hour_ago" I've installed "TeraTerm" in the Windows systems, (complete with the SSH = patch), and its sorta talking to unix (its got no problem with regular telnet login), but I've obviously not understood something = about this private / public keys stuff because it refuses to=20 accept either the private or the public keys that I copied from the = FreeBSD /home/username directory. =20 "man ssh" says "The user creates his/her RSA key pair blah blah blah = ..... then copy the identity.pub to some directory on=20 the remote machine." Now thats all very well if the remote machine = happens to be another unix box, but where on earth does one find a "HOME/.ssh/authorized_keys" file or directory in a Windows = system ????????=20 I get a "fatal: Timeout before authentication for xxx.xxx.xxx.xxx" = message from FreeBSD, but I guess thats just the FreeBSD=20 system spitting the dummy at a key it doesn't like. Would someone please enlighten me on just how I go about setting up keys = that are acceptable to both FreeBSD & Windows,=20 and if theres any sort of hocus pocus is involved in getting the key/s = from unix to windows without changing the things. ------=_NextPart_000_0921_01C05959.1C090B10 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

I'm trying to configure SSH login to a = 4.2 RELEASE=20 system from various Windows machines. It certainly appears to be a =

step forward in securing servers from = the moron=20 element that gets its thrills from wanton vandalism, however as with = most=20

new things in unix the = documentation quite=20 sparse as far as explaining

"exactly_how_do_I_do_this_from_scratch_when_I_ only_first=20 _stumbled_across_ the beast_an_hour_ago"

I've installed "TeraTerm" in the = Windows systems,=20 (complete with the SSH patch), and its sorta talking to unix (its got no = problem

with regular telnet = login), but I've obviously not understood something = about this private / public keys stuff because it = refuses to=20

accept either the private or=20 the public keys that I copied from the FreeBSD /home/username=20 directory.

"man ssh" says "The user creates = his/her RSA key=20 pair blah blah blah ..... then copy the identity.pub to some = directory on=20

the remote machine." Now thats = all very well=20 if the remote machine happens to be another unix box, but where on = earth=20 does

one find a "HOME/.ssh/authorized_keys" = file or=20 directory in a Windows system = ????????=20

I get a "fatal: Timeout before = authentication for=20 xxx.xxx.xxx.xxx" message from FreeBSD, but I guess thats just the = FreeBSD=20

system spitting the=20 dummy at a key it doesn't like.

Would someone please enlighten me on = just how I go=20 about setting up keys that are acceptable to both FreeBSD & Windows, =

and if theres any sort of hocus = pocus is=20 involved in getting the key/s from unix to windows without changing the=20 things.

------=_NextPart_000_0921_01C05959.1C090B10-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message