Putty and SSH of Multinet

[Wim Van den Wyngaert]

I'm using SSH 5.0.1 of multinet combined with putty 0.57. I generated a key on the PC and transfered the public part to VMS (binary and then set file/at=rfm=stmlf).

When I run putty towards the multinet ssh server, I get the messages

*** Authenticating with public key "dsa-key-20070201" ***
Then
*** Access denied ***
Then
*** WIM@node's password ***

On the server I got
*** WARNING: Public key operation failed for wim ***

Anyone an idea what to do next ?
I use 256 bits DSA key.

Wim

[Wim Van den Wyngaert]

Here is the server trace when debug level is 50 (user wim is now sysmgr_wvw). It looks like the key is OK but something is still wrong with publickey. The key file is called ID_PC.

Wim

[Jim_McKinney]

MultiNet uses the F-Secure codebase. Does Putty produce an OpenSSH or SECSH (F-Secure) style key? If it's an OpenSSH key then you'll either need to convert it or re-generate it in the SECSH format.

[Wim Van den Wyngaert]

I generated a dsa key in putty. Then I asked "export to openssh". Then I did save private key.

I ftp'd the private key to vms. Converted it with success to SSH2 and then extracted the public key.

Still the same problem.

Wim (gone till monday)

[Martin Vorlaender]

Wim,

>>>
I generated a dsa key in putty. Then I asked "export to openssh". Then I did save private key.
<<<

Skip that "export to openssh" step. Like Jim_McKinney wrote, Process uses SECSH format, and PuTTY uses the same.

>>>
I ftp'd the private key to vms. Converted it with success to SSH2 and then extracted the public key.
<<<

The private key should *NEVER* be transferred anywhere. Transfer the public key. DON'T convert. Add a reference to the public key file to SYS$LOGIN:[.SSH2]AUTHORIZATION. (see http://www.process.com/tcpip/mndocs/MN%20v5.0%20Installation%20Administrator%20Guide/Ch30.htm#E55E302)

Of course, the MultiNet's SSHD2_CONFIG file has to list PublicKey in the AllowedAuthentications.

You can use http://www.process.com/tcpip/mndocs/MN%20v5.0%20User%20Guide/Ch07.htm#E55E35 as a guideline (substitute PuTTY for the MultiNet SSH client).

HTH,
Martin

[Ian Miller.]

Note also putty 0.59 is now available

[Wim Van den Wyngaert]

Martin,

If you check my enclosure trace file, you find "the key matched". Thus it's not the setup of SSH but the file/contents that's causing the problem.

Wim

[Wim Van den Wyngaert]

Started alover again. This time using rs1 1024 bits, this time with passphrase (before I used none). Same problem. The public key file is accepted, a passphrase is prompted for and end.

In sshd log file :
Pubkey for server is of type 'if-modn'
Scheme for RSA public key was set to rsa-pkcs1-sha1

and then again WARNING... failed

Wim

[Wim Van den Wyngaert]

Here is a debug level 7 trace for those who now what to look for. Search for 2nd occurence of WARNING to get to the problem point.

Wim

[Wim Van den Wyngaert]

Retried with development putty 0.59 plus some changes(with newly generated rsa key). Same problem.

Wim