HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

SSH Authentication Failed

 
SOLVED
Go to solution

SSH Authentication Failed



I will try and make this short


My coworker has been able to ssh to a server from a Putty session on his pc.

So we know the public and private keys work in that senario.

On the tru64 side of the gs160 I ftp the private client key to OpenVMS and converted the file to Stream_LF as I found out in the documentation.

Both on the tru64 side and OpenVMS side the SSH session indicates the public key has been accepted and I did find it in the
SYS$SYSDEVICE:[TCPIP$SSH.SSH2.HOSTKEYS] directory.

**********************************************
Host key saved to ssh2/hostkeys/key_gs160.pub
host key for gs160, accepted by system Tue Aug 23 2005 22:39:57
warning: Authentication failed.
Disconnected; no more authentication methods available (No further authenticatio
n methods available.).
**********************************************

Any help here would be very great

Thank you all again

Robert J.

3 REPLIES
Robert_Boyd
Respected Contributor
Solution

Re: SSH Authentication Failed

Robert,

Could you provide the commands that you're using that generate the failure you show here?

Robert
Master you were right about 1 thing -- the negotiations were SHORT!

Re: SSH Authentication Failed

Thank you for your help


This is kind of tuff sleading on this issue

At this point I have been able to use OpenVMS as a SSH server in the context of downloading Putty setting an IP address and using I guess just password based authentication. One small step for mindkind. I was able to gain a $ prompt and do some basic commands like $show system


Without going into to much troubleshooting at this point in regards to the use of Public/Private key pairs. There may be a problem with the Keys that were generated at this unix box. Which is a custom linux system.


The first thing I did was to ftp this private key file icat.PPK from the tru64 side of the gs160 this file was generated on the other custom linux box

on the OpenVMS side of the gs160 I converted the file into Stream_LF as shown below in the dir/full output

********************************************

icat.PPK;3 File ID: (8433,2,0)
Size: 2/3 Owner: [1,1]
Created: 23-AUG-2005 15:25:58.43
Revised: 23-AUG-2005 15:25:58.48 (1)
Expires:
Backup:
Effective:
Recording:
Accessed:
Attributes:
Modified:
Linkcount: 1
File organization: Sequential
Shelved state: Online
Caching attribute: Writethrough
File attributes: Allocation: 3, Extend: 0, Global buffer count: 0
No version limit
Record format: Stream_LF, maximum 0 bytes, longest 65 bytes
Record attributes: Carriage return carriage control
RMS attributes: None
Journaling enabled: None
File protection: System:RWED, Owner:RWED, Group:RE, World:
Access Cntrl List: None
Client attributes: None

********************************************


I am getting regected from both the linux box and the tru64 using this private key

at this stage i want to ask my coworker to regenerate the key pairs and start over.

my coworker get authenticated to the linux box but not on tru64

This is starting to drive me crazy. As long as he get in to the linux box from his PC he does not want to regen any keys at this stage

Any hints and I will keep you posted

Thanks Robert J
Robert_Boyd
Respected Contributor

Re: SSH Authentication Failed

Which directory did you put the icat.PPK file in?

See this documentation page for the rules about how to set up keys correctly:

http://h71000.www7.hp.com/DOC/732final/aa-rvbua-te/aa-rvbua-te.html

Robert
Master you were right about 1 thing -- the negotiations were SHORT!