On Fri, 2003-08-01 at 10:04, System Administrator wrote: > see below... > On Thursday 31 July 2003 21:38, Bret Hughes wrote: > > On Thu, 2003-07-31 at 18:07, System Administrator wrote: > > > Yes, this is a perfect example of why we should 'just get rid of > > > windows'. But.....that is not an option right now. > > > > > > I am trying to setup SSH with public-key encription to a RH8 box. I am > > > running OpenSSH 3.4p2. All default setup. > > > > > > Of course the other *UX boxes manage just fine (thanks to a VERY good > > > write-up from akadia.com). > > > > > > The Windows (NT,2000) systems, on the other hand, can't seem to get it > > > right. I have tried ssh secure shell. I found writeups on the website. > > > But it Didn't work. but not diags to see why. I try putty and geta > > > message saying "Key is of wrong type (PuTTY SSH2 private key)" . If I > > > look at the actual entry (authorized_keys) in the .ssh folder, it list > > > the entry as "public key". Again I followed the documentation to > > > generate the keys. At least I think I did. > > > > > > Any insights will be appreciated. > > > -- > > > > Did do the key conversion before you put the public key in the other > > host? Are you sure you generated a type 2 key? > Yes and Yes. I actually went throught the process several times. The last > time I made sure that I documented each step. > > > > You really did not give us much to go on. > If there is more info I can give to assist you "please" let me know. I see no > security issues in providing the information. I have full scale code > developement going on and they are using a makeshift document control setup > until I can get this going.
Ok one caveat, I have only done this once from a W2000 box and have slept since then. I have setup hundreds of openssh boxes though. Assumptions: The linux host is setup so that the same user can connect from another linux box. User specific is important because perms on the authorized_keys file can cause failures. The windows generated public key has been converted to openssh format and has been installed in the user's ~/.ssh/authorized_keys[2] file The first thing I would do is put the ssh server into debug mode. If you can tell everyone to leave it alone for a minute: service sshd stop as root from a command prompt: sshd -d -d # additional -d for even more output This will put the server in a state that only one connection will be processed and spit a bunch of stuff to stderr. try to connect from the windows box using whatever debug options exist in the client. take a look at the output and see if you can tell what is going wrong. If not post the output to the list. someone here will be able to figure it out. Bret -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
