openssh bugs - Jun 2018 - [Bug 2878] New: scp protocol error: mtime.sec not present

https://bugzilla.mindrot.org/show_bug.cgi?id=2878

            Bug ID: 2878
           Summary: scp protocol error: mtime.sec not present
           Product: Portable OpenSSH
           Version: 7.7p1
          Hardware: ix86
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: scp
          Assignee: unassigned-bugs at mindrot.org
          Reporter: cnewman at mgage.com

Linux server-12b 3.10.0-862.3.2.el7.x86_64 #1 SMP Mon May 21 23:36:36
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux



On executing

scp  server-12a:~userHome/.chris .

Error is received:
protocol error: mtime.sec not present


Error is appearing ONLY when the login script at the sourceServer has
output.  When all output is suppressed, scp completed successfully.

Reproduced many times in bash shell and even produced by simply putting 
echo "testing" in the .bashrc on the login script of the source
server.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=2878

Damien Miller <djm at mindrot.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |djm at mindrot.org

--- Comment #1 from Damien Miller <djm at mindrot.org> ---
Login scripts should not produce any output for non-interactive
sessions. 

If "ssh server-12a true" produces output then that will break sftp and
scp.

-- 
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.

https://bugzilla.mindrot.org/show_bug.cgi?id=2878

--- Comment #2 from Christopher Newman <cnewman at mgage.com> ---
Is that new behavior of openssh in Cent7?  Because there's no problem
or error with Cent6 with the exact same .bashrc .   That's how we
encountered it.  Migrating to our new Cent7 systems and just copying
over the same .bashrc and home directories.

Linux server6 2.6.32-696.18.7.el6.x86_64 #1 SMP Thu Jan 4 17:31:22 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux

No error on sftp nor scp of the same file and the same login .bashrc. 
And the same output on login.

-- 
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=2878

Darren Tucker <dtucker at dtucker.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dtucker at dtucker.net

--- Comment #3 from Darren Tucker <dtucker at dtucker.net> ---
no, this behaviour dates back more than 30 years to rcp from which scp
descended.  if your behaviour has changed with your new OS release I'd
be looking for behaviour changes in the shell or your system wide login
scripts.

-- 
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=2878

--- Comment #4 from Christopher Newman <cnewman at mgage.com> ---
well I guess feel free to close as this has been extremely unhelpful as
I showed I simply pick-n-lift scripts and the only change was the OS...
and now broken... and you're saying it can't be possibly working in
previous version, and it is... works in Cent6 .  works in Cent5.....
and that's within your 30 year explanation.  So thanks for your
theoretical text book answer.

-- 
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=2878

Damien Miller <djm at mindrot.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|NEW                         |RESOLVED

-- 
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=2878

--- Comment #5 from Darren Tucker <dtucker at dtucker.net>
---
> you're saying it can't be possibly working in previous version
no, I said "I'd be looking for behaviour changes in the shell or your
system wide login scripts".

Quoting bash(1):

"""
       An interactive shell is one whose standard input and  output 
are  both
       connected  to  terminals  (as  determined by isatty(3)), or one
started
       with the -i option.  PS1 is set and $- includes i if bash  is 
interac-
       tive, allowing a shell script or a startup file to test this
state.

       Login shells:
         On login (subject to the -noprofile option):
               if /etc/profile exists, source it.

               if ~/.bash_profile exists, source it,
                 else if ~/.bash_login exists, source it,
                   else if ~/.profile exists, source it.

         On exit:
               if ~/.bash_logout exists, source it.

       Non-login interactive shells:
         On startup (subject to the -norc and -rcfile options):
               if ~/.bashrc exists, source it.
[...]

       If  Bash  is  invoked  as  sh,  it tries to mimic the behavior
of sh as
       closely as possible.  For a login shell, it  attempts  to 
source  only
       /etc/profile  and ~/.profile, in that order.  The -noprofile
option may
       still be used to disable this behavior.  A shell invoked as sh
does not
       attempt to source any other startup files.
"""

Which of those things did you check and what did you find?

-- 
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=2878

Christopher Newman <cnewman at mgage.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|INVALID                     |WONTFIX
             Status|RESOLVED                    |CLOSED

--- Comment #6 from Christopher Newman <cnewman at mgage.com> ---
both... and thank you for "resolving" ..
"open-source-community" .
gotta love it

-- 
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.

https://bugzilla.mindrot.org/show_bug.cgi?id=2878

Damien Miller <djm at mindrot.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|WONTFIX                     |INVALID

--- Comment #7 from Damien Miller <djm at mindrot.org> ---
You got an exact description of what is wrong and how to diagnose it,
which is considerably more than you paid for.

-- 
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.