Bug 1259925
Summary: | scp between Fedora Rawhide and Fedora 22 does not work with strange output | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Randy Barlow <rbarlow> |
Component: | openssh | Assignee: | Petr Lautrbach <plautrba> |
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | jjelen, mattias.ellert, mgrepl, plautrba, tmraz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-09-09 21:06:07 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: | |
Embargoed: |
Description
Randy Barlow
2015-09-03 20:01:27 UTC
Two more data points: 0) I am able to scp in the reverse direction. I.e., I can initiate the scp from the Fedora 22 machine into the Fedora Rawhide machine and push a file. 1) I am able to initiate an scp from Rawhide and pull a file from a Gentoo system. Perhaps this indicates some incompatibility that only exists between Rawhide and 22? That seems unlikely, however. I wish I got more output with the -v flag! I was trying to introduce the behaviour you described but without any success:
rawhide:
[root@localhost tmp]# scp 192.168.100.211:~/.bashrc .
Password:
.bashrc 100% 176 0.2KB/s 00:00
[root@localhost tmp]# echo $?
0
> /:-------------:\
this is actual string you see in your terminal during transfer?
Last change that was in scp program was related to progress-meter in openssh-6.9p1-4 + 0.9.3-6, which went into Fedora 22. Can you try the same with -q option to disable progress-meter?
What do you have in your sshd_config on Fedora 22? Which type of authentication are you using? Normal ssh sessions works fine?
Yes, it actually printed a line with /:-------------:\ in colorful text. Strange, right? I am now unable to reproduce this problem (perhaps due to an update in some dependency?) Sorry for the noise! |