Fail To Execute SCP Command To Gateway After Upgrade To 11.1

Products

• CA API Gateway

Issue/Introduction

After upgrading to Gateway version 11.1 we can no longer scp to the gateway host and receive the following error:

# scp MyFile.txt UserName@GatewayHostName:/MyDirectory

Corrupted MAC on input.
ssh_dispatch_run_fatal: Connection to xx.xx.xx.xx port 22: message authentication code incorrect

Environment

CA API Gateway 11.1

Cause

The default list of MACs within GW 11.1 was modified.

Resolution

You can specify which MAC to use with the scp command by executing something along the following:

# scp -o MACs=hmac-sha2-512 MyFile.txt UserName@GatewayHostName:/MyDirectory

 

The scp command will now execute successfully.

Additional Information

This situation has only been observed with older versions of ssh/scp clients.  Please look to upgrade your current client to the latest version to avoid having to specify the additional command line options for the command to execute successfully.