Not able to transfer file from VMS to Unix without using password

[Wim Van den Wyngaert]

The authorized_keys file, isn't that a SSH1 file ? I used it once with for SSH tunnels and just pasted the public key into it.

To get KEA!X in the putty tunnel in ssh2 took me several days.

Wim

[santoshpandey02]

Wim,

I have tried with IP address but failed.
Also, I am not aware of switch case in the username?

in the given link Doug is telling that he is able to transfer file from VMS to Unix successfully, but steps are not given in the link
http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1208795880611+28353475&threadId=1138560

Some of his commnets are like this:

=====================================
Hello everyone:
I've been wrestling with the setup of sftp from a vms system to a unix system, utilizing batch mode (e.g. sftp "-B" "filename.com" remoteuser@remotehost.com)

I got it working and now the application support group has given me a list of accounts which require access to this function.

No problem, I simply have to copy the public keys and the identification. file to the ssh2 directory of each user and that's it.

=====================================

[Wim Van den Wyngaert]

Can't help because I'm on multinet and old 7.3. There are 2 versions of the protocol : SSH1 and SSH2. I think you did a mix.

Switch case : try in lowercase username and also in uppercase.

Wim

[Steven Schweda]

> I'd also start with a simple SSH command,
> like "ssh -v user@unix_host" rather than any
> SCP command, until you get that much to work.

Still true.

Anything interesting in the system logs on
the (still unidentified?) UNIX system?

ls -ld .ssh
ls -l .ssh

> 2. I have found here that SSH sercure shell
> is available on source but OpenSSH is
> available on target, Is that creating
> problem here?

Probably not an insoluble problem. Around
here:

alp $ tcpip show version

HP TCP/IP Services for OpenVMS Alpha Version V5.4 - ECO 6
on a COMPAQ Professional Workstation XP1000 running OpenVMS V7.3-2

alp $ ssh "-V"
alp$dka0:[sys0.syscommon.][sysexe]tcpip$ssh_ssh2.exe: SSH Secure Shell OpenVMS (
V5.5) 3.2.0 on COMPAQ Professional Workstation - VMS V7.3-2


alp $ ssh sms@ra
Authentication successful.
Last login: Wed Apr 23 08:32:44 2008 from alp-l.antinode.
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
-bash-3.1$ ssh -V
Sun_SSH_1.1, SSH protocols 1.5/2.0, OpenSSL 0x0090704f
-bash-3.1$


alp $ ssh sms@dy
Authentication successful.
Last login: Wed Apr 23 08:44:18 2008 from alp-l.antinode.

dy $ ssh -V
OpenSSH_4.3p2-hpn, OpenSSL 0.9.7i 14 Oct 2005
HP-UX Secure Shell-A.04.30.006, HP-UX Secure Shell version
dy $


alp $ ssh sms@smacg4
Authentication successful.
Last login: Tue Apr 22 14:04:47 2008
Welcome to Darwin!
smacg4:~ sms$ ssh -V
OpenSSH_4.7p1, OpenSSL 0.9.7l 28 Sep 2006
smacg4:~ sms$


Of course, those are _my_ UNIX (or UNIX-like)
systems, not yours, and yours could be
different.

[Amin Wahi]

I ran into the same issue. I found a fix that worked for me. Make sure "~/.ssh/authorized_keys" in your destination server has the permissions set to mode 600. All your other steps are correct.

Regards,
Amin