Bug 1022552

Summary: SCP inappropriate truncate error when copying to FIFO
Product: Red Hat Enterprise Linux 5 Reporter: Konstantin Lepikhov <klepikho>
Component: opensshAssignee: Petr Lautrbach <plautrba>
Status: CLOSED WONTFIX QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.9CC: jbuchta
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-17 15:13:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
fixes the problem, it is an upstream fix none

Description Konstantin Lepikhov 2013-10-23 13:55:32 UTC 
Description of problem:
when copying a file to fifo over scp, remote side of scp sents back to the client error telling "truncate: Invalid argument"

Version-Release number of selected component (if applicable):
RHEL5.9
# rpm -qa|fgrep openssh
openssh-4.3p2-82.el5
openssh-clients-4.3p2-82.el5
openssh-server-4.3p2-82.el5

How reproducible:
always


Steps to Reproduce:
1. create a fifo on the remote side:
$ mkfifo testfifo

2. read from the fifo:
$ cat testfifo

3. send some file to remote fifo:
$ scp ~/tmp/input user@host:testfifo


Actual results:
$ scp ~/tmp/input user@host:testfifo
input                                                                                                                               100%  189     0.2KB/s   00:00
scp: testfifo: truncate: Invalid argument
$


Expected results:
$ scp ~/tmp/input user@host:testfifo
input                                                                                                                               100%  189     0.2KB/s   00:00
$


Additional info:
bug is fixed in an upstream version of openssh 4.7

attached patch fixes the problem and is the same as an upstream fix
Comment 1 Konstantin Lepikhov 2013-10-23 14:02:09 UTC 
Created attachment 815425 [details]
fixes the problem, it is an upstream fix
Comment 2 Petr Lautrbach 2014-01-17 15:13:43 UTC 
This Bugzilla has been reviewed by Red Hat and is not planned on being
addressed in Red Hat Enterprise Linux 5, and therefore will be closed.
If this bug is critical to production systems, please contact your Red
Hat support representative and provide sufficient business
justification. Issue is already fixed in RHEL-6