Bug ID 1097193: Unable to SCP files using WinSCP or relative path name

Last Modified: Sep 27, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
17.0.0, 16.1.2.2, 15.1.6, 15.1.5.1, 14.1.5, 14.1.4.6, 13.1.5

Fixed In:
16.1.3.1

Opened: Apr 11, 2022
Severity: 2-Critical

Symptoms

When attempting to retrieve a file with WinSCP, you receive an error dialog and the session will be terminated: "SCP Protocol error: Invalid control record (r; elative addresses not allowed) Copying files from remote side failed." If attempting to transfer a file by relative path with a command line utility the transfer will fail with the message: "relative addresses not allowed"

Impact

No longer able to use WinSCP to retrieve files such as packet captures, log archives, or other diagnostic data from the BIG-IP system.

Conditions

-- Running BIG-IP version with fix for ID 915981 -- Using WinSCP set to use SCP protocol to retrieve files from a BIG-IP system. -- Using a relative remote path to transfer a file with command line scp utility.

Workaround

Use a command line SCP tool that allows specifying an absolute path for the source and/or destination file (a path that starts with a forward slash /), when the source and/or destination locations are a BIG-IP device. If the user ID is permitted to do so, you may use WinSCP in SFTP mode.

Fix Information

None

Behavior Change