bugzilla-daemon at mindrot.org
2014-Mar-12  00:43 UTC
[Bug 2210] New: scp -q isn't quiet when copying between two remote hosts
https://bugzilla.mindrot.org/show_bug.cgi?id=2210
            Bug ID: 2210
           Summary: scp -q isn't quiet when copying between two remote
                    hosts
           Product: Portable OpenSSH
           Version: 6.0p1
          Hardware: PPC
                OS: AIX
            Status: NEW
          Severity: normal
          Priority: P5
         Component: scp
          Assignee: unassigned-bugs at mindrot.org
          Reporter: michael.j.tosh at lmco.com
OpenSSH_6.0p1, OpenSSL 1.0.1e 11 Feb 2013
When using banners in SSH, scp -q will only suppress banners for one
remove host, but not two.  See the following example, using SSH 6.0p1
compiled on AIX 5.3 and distributed by IBM.
root at host3:/tmp
--> scp -q host1:/tmp/x.out /tmp/x.out.host1
root at host3:/tmp
--> scp -q /tmp/x.out host2:/tmp/x.out.host3
root at host3:/tmp
--> scp -q host1:/tmp/x.out host2:/tmp/x.out.host1
#################################################################
#               Hostname:               host2                   #
#################################################################
root at host3:/tmp
-->
-- 
You are receiving this mail because:
You are watching the assignee of the bug.
bugzilla-daemon at mindrot.org
2024-Dec-06  15:33 UTC
[Bug 2210] scp -q isn't quiet when copying between two remote hosts
https://bugzilla.mindrot.org/show_bug.cgi?id=2210
Damien Miller <djm at mindrot.org> changed:
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |djm at mindrot.org
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED
--- Comment #1 from Damien Miller <djm at mindrot.org> ---
I think this got fixed when we converted scp to use sftp internally. It
doesn't produce output for me with -q anyway. Please reopen if this
isn't the case for you
-- 
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.