On May 17, 2012, at 5:49 AM, Thomas Pfau wrote: > I understand this problem is fixed with the new ssh that comes with OpenVMS > 8.4. Prior to this, scp does not work to openssh systems.
It seems not, actually. With a server that looks like: $ tcpip show vers HP TCP/IP Services for OpenVMS Industry Standard 64 Version V5.7 - ECO 2 on an HP rx2600 (1.50GHz/6.0MB) running OpenVMS V8.4 coming from an OS X client (with remote address changed to protect the guilty): % scp -v test.txt craig@192.168.1.2: Executing: program /usr/bin/ssh host 192.168.1.2, user craig, command scp -v -t -- . OpenSSH_5.6p1, OpenSSL 0.9.8r 8 Feb 2011 debug1: Reading configuration data /Users/craig/.ssh/config debug1: Reading configuration data /etc/ssh_config debug1: Applying options for * debug1: Connecting to 192.168.1.2 [192.168.1.2] port 22. debug1: Connection established. debug1: identity file /Users/craig/.ssh/id_rsa type 1 debug1: identity file /Users/craig/.ssh/id_rsa-cert type -1 debug1: identity file /Users/craig/.ssh/id_dsa type -1 debug1: identity file /Users/craig/.ssh/id_dsa-cert type -1 debug1: Remote protocol version 2.0, remote software version 3.2.0 SSH OpenVMS V5.5 VMS_sftp_version 3 debug1: no match: 3.2.0 SSH OpenVMS V5.5 VMS_sftp_version 3 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.6 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: sending SSH2_MSG_KEXDH_INIT debug1: expecting SSH2_MSG_KEXDH_REPLY debug1: Host '192.168.1.2' is known and matches the DSA host key. debug1: Found key in /Users/craig/.ssh/known_hosts:13 debug1: ssh_dss_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received Welcome to HP OpenVMS Industry Standard 64 Operating System, Version V8.4 debug1: Authentications that can continue: publickey,password debug1: Next authentication method: publickey debug1: Offering RSA public key: /Users/craig/.ssh/id_rsa debug1: Server accepts key: pkalg ssh-rsa blen 149 debug1: Authentication succeeded (publickey). Authenticated to 192.168.1.2 ([192.168.1.2]:22). debug1: channel 0: new [client-session] debug1: Entering interactive session. debug1: Sending environment. debug1: Sending env LANG = en_US.UTF-8 debug1: Sending command: scp -v -t -- . scp1 compatibility mode is not supported. So while I probably had the nomenclature and version numbers confused in my previous post, there is definitely something still wrong with agreeing on a mutually acceptable version of something. It looks like it's a very old problem for servers that do not support multiple protocols: <http://www.snailbook.com/faq/scp-ossh-to-ssh2.auto.html>. If someone finds an open source scp2 client, please holler. ________________________________________ Craig A. Berry mailto:craigbe...@mac.com "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser
