System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

scp1 compatibility mode is not supported.

 
Sac77
Advisor

scp1 compatibility mode is not supported.

I am trying to scp from hp-ux to vms server, but got error "scp1 compatibility mode is not supported.".

Kindly advise, please see the attached logs -

$ sftp -F ssh_config ftp_annc@10.97.108.2
Connecting to 10.97.108.2...
sftp> pwd
Remote working directory: /DKA100/omex/gen/cur/ls1
sftp> dir
ANNC.TXT;1 ANNC_____-090121.TXT;1 ANNC_____-090130.TXT;1
FTP_ANNC.DIR;1 SSH2.DIR;1 TCPIP$FTP_SERVER.LOG;27
TCPIP$SSH_RCMD.LOG;1 TESTSCP.TXT;1
sftp> put test.log
Uploading test.log to /DKA100/omex/gen/cur/ls1/test.log
test.log 100% 231KB 230.9KB/s 230.9KB/s 00:00
sftp> ll
Invalid command.
sftp> dir
ANNC.TXT;1 ANNC_____-090121.TXT;1 ANNC_____-090130.TXT;1
FTP_ANNC.DIR;1 SSH2.DIR;1 TCPIP$FTP_SERVER.LOG;27
TCPIP$SSH_RCMD.LOG;1 TEST.LOG;1 TESTSCP.TXT;1
sftp> rm TEST.LOG;1
Removing /DKA100/omex/gen/cur/ls1/TEST.LOG;1
sftp> dir
ANNC.TXT;1 ANNC_____-090121.TXT;1 ANNC_____-090130.TXT;1
FTP_ANNC.DIR;1 SSH2.DIR;1 TCPIP$FTP_SERVER.LOG;27
TCPIP$SSH_RCMD.LOG;1 TESTSCP.TXT;1
sftp> quit


$ scp -F ssh_config test.log ftp_annc@10.97.108.2:
scp1 compatibility mode is not supported.
$ more ssh_config
# $OpenBSD: ssh_config,v 1.21 2005/12/06 22:38:27 reyk Exp $

# This is the ssh client system-wide configuration file. See
# ssh_config(5) for more information. This file provides defaults for
# users, and the values can be changed in per-user configuration files
# or on the command line.

# Configuration data is parsed as follows:
# 1. command line options
# 2. user-specific file
# 3. system-wide file
# Any configuration value is only changed the first time it is set.
# Thus, host-specific definitions should be at the beginning of the
# configuration file, and defaults at the end.

# Site-wide defaults for some commonly used options. For a comprehensive
# list of available options, their meanings and defaults, please see the
# ssh_config(5) man page.

# Host *
# ForwardAgent no
# ForwardX11 no
# RhostsRSAAuthentication no
RSAAuthentication yes
# PasswordAuthentication yes
# PasswordAuthentication no
# HostbasedAuthentication no
# BatchMode no
# CheckHostIP yes
# AddressFamily any
# ConnectTimeout 0
StrictHostKeyChecking no
# IdentityFile ~/.ssh/identity
# IdentityFile ~/.ssh/id_rsa
IdentityFile ~/.ssh/anc50dev
# IdentityFile ~/.ssh/id_dsa
# GSSAPIAuthentication no
# GSSAPIDelegateCredentials no
# Port 22
Protocol 2,1
HashKnownHosts yes
HPNDisabled yes
# Cipher 3des
# Ciphers aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes2
56-cbc
# EscapeChar ~
# Tunnel no
# TunnelDevice any:any
# PermitLocalCommand no


$ scp test.log ftp_annc@10.97.108.2:
ftp_annc@10.97.108.2's password:
scp1 compatibility mode is not supported.


$ scp -v -F ssh_config test.log ftp_annc@10.97.108.2:
Executing: program /opt/ssh/bin/ssh host 10.97.108.2, user ftp_annc, command scp
-v -t .
OpenSSH_5.1p1+sftpfilecontrol-v1.2-hpn13v5, OpenSSL 0.9.8j 07 Jan 2009
HP-UX Secure Shell-A.05.10.046, HP-UX Secure Shell version
debug1: Reading configuration data ssh_config
debug1: Connecting to 10.97.108.2 [10.97.108.2] port 22.
debug1: Connection established.
debug1: identity file /home/stkapp/.ssh/anc50dev type -1
debug1: Remote protocol version 2.0, remote software version 3.2.0 SSH Secure Sh
ell OpenVMS V5.5 VMS_sftp_version 3
debug1: no match: 3.2.0 SSH Secure Shell OpenVMS V5.5 VMS_sftp_version 3
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.1p1+sftpfilecontrol-v1.2-hpn13v5
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: AUTH STATE IS 0
debug1: REQUESTED ENC.NAME is 'aes128-cbc'
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: REQUESTED ENC.NAME is 'aes128-cbc'
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: sending SSH2_MSG_KEXDH_INIT
debug1: expecting SSH2_MSG_KEXDH_REPLY
debug1: Host '10.97.108.2' is known and matches the DSA host key.
debug1: Found key in /home/stkapp/.ssh/known_hosts:1
debug1: ssh_dss_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Trying private key: /home/stkapp/.ssh/anc50dev
debug1: read PEM private key done: type RSA
debug1: Authentication succeeded (publickey).
debug1: Final hpn_buffer_size = 2097152
debug1: HPN Disabled: 1, HPN Buffer Size: 2097152
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: Sending command: scp -v -t .
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: channel 0: free: client-session, nchannels 1
scp1 compatibility mode is not supported.
debug1: fd 0 clearing O_NONBLOCK
debug1: fd 1 clearing O_NONBLOCK
Transferred: sent 1816, received 4520 bytes, in 0.4 seconds
Bytes per second: sent 4435.9, received 11040.9
debug1: Exit status 0
$
4 REPLIES
Steven Schweda
Honored Contributor

Re: scp1 compatibility mode is not supported.

> [...] from hp-ux to vms server, [...]

See? It's more interesting already.

Potentially useful info on the VMS side:

TCPIP SHOW VERSION

On the HP-UX side:

uname -a

A quick Google search for "scp1 compatibility
mode is not supported" found:

http://unix.derkeiler.com/Newsgroups/comp.os.vms/2005-09/1254.html

which suggests that you may be stuck with
SFTP, unless you can find a way to get the
SCP client to use scp2.
Sac77
Advisor

Re: scp1 compatibility mode is not supported.

Here you go -

TSDC02_SGE> TCPIP SHOW VERSION

HP TCP/IP Services for OpenVMS Alpha Version V5.6 - ECO 2
on an hp AlphaServer ES47 7/1000 running OpenVMS V8.3


anc50dev [/]#uname -a
HP-UX anc50dev B.11.23 U 9000/800 3902691228 unlimited-user license
Matti_Kurkela
Honored Contributor

Re: scp1 compatibility mode is not supported.

The message "scp1 compatibility mode is not supported" comes from the remote server.

According to the debug output, the remote SSH server version string is "3.2.0 SSH Secure Shell OpenVMS V5.5 VMS_sftp_version 3" which is an old version of a commercial product from ssh.com.

The 3.2.* series of SSH packages from ssh.com had a nasty trick: they don't support scp unless the scp client from SSH version 1.* is also installed. In the 3.2.* series, ssh.com attempted to standardize on sftp protocol for file transfer. The traditional scp protocol (which is still used by OpenSSH scp) was called "scp1 compatibility mode" regardless of whether the SSH protocol version 1 or 2 was used.

Yes, I know the ssh.com 3.2.* has a command named "scp". But it does not use the "scp" file transfer protocol: it uses the SFTP extension of the SSH protocol version 2 instead.

The traditional/OpenSSH scp works by opening a regular SSH connection to the remote host and running a "scp -f" ("from") or "scp -t" ("to") command on the remote host.

The ssh.com 3.2.* server process intercepts these commands and runs them with "scp1" if it is available; if not, the error message "scp1 compatibility mode is not supported" is sent.

The problem is not fixable in the HP-UX end. As a work-around, you can use SFTP to transfer files. It is not as convenient as using scp, but using the "-b " option may help. See "man sftp" for details.

To fix the problem, some things must be done in the OpenVMS end:
- update the ssh.com 3.2.* SSH server process to a current version, or perhaps switch over to OpenSSH-based version, or
- install a "scp1" command to the OpenVMS server, so that the existing SSH server process can find and use it.

MK
MK
Steven Schweda
Honored Contributor

Re: scp1 compatibility mode is not supported.

> [...] Version V5.6 - ECO 2 [...]

> [...] some things must be done in the
> OpenVMS end: [...]

Well, there is an ECO 3, but HP seems no
longer to publish the release notes in any
easily accessible way:

ftp://ftp.itrc.hp.com/openvms_patches/layered_products/alpha/DEC-AXPVMS-TCPIP-V0506-9ECO3-1.txt

[...]
See the TCPIP56ECO03.RELEASE_NOTES file included in the kit.
[...]

_That's_ convenient, all right. I'm too
lazy to look, but I doubt that it would
help.

> The problem is not fixable in the HP-UX
> end.

And probably not much more on the VMS end.