openssh bugs - Mar 2021 - [Bug 3287] New: Update to 8.5p1 on Arch-derived distro breaks file browser access to a FreeBSD share in my LAN

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

            Bug ID: 3287
           Summary: Update to 8.5p1 on Arch-derived distro breaks file
                    browser access to a FreeBSD share in my LAN
           Product: Portable OpenSSH
           Version: 8.5p1
          Hardware: amd64
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: ssh
          Assignee: unassigned-bugs at mindrot.org
          Reporter: vintongunker64 at gmail.com

Created attachment 3487
  --> https://bugzilla.mindrot.org/attachment.cgi?id=3487&action=edit
Screen shot # 2 - error message

I am a retired dude so this is a personal use case.

I have a laptop running Artix with cinnamon desktop environment, and a
desktop PC running Manjaro using the suckless dwm window manager as my
daily drivers.  On both of these, I prefer NEMO as the file explorer.

I also have a FreeBSD box that is my home file server.

Both of the linux machines have been stable for several months, and on
each I have had a shortcut established in Nemo to my home directory on
the FreeBSD box.  That has given me no problem heretofore.

Recently, arch has pushed down the openssh 8.5 package.  I found that
the upgrade breaks my shortcut to the FreeBSD box on both my linux
machines.

Work arounds are to just use command line sftp to move files or map the
FreeBSD to local file system in linux via sshfs mounting.

As soon as I realized the 8.5 package update was the breaking change, I
blacklisted package manager for openssh and rolled back to 8.4 and the
problem completely went away. 



Here are symptoms / circumstances

* I have static LAN IP addresses assigned to all 3 machines mentioned
above on my router per MAC address, and I built my shortcuts per
x.x.x.x addresses, not machine names.

* On either machine, attempt to open the link to my FreeBSD in Nemo
("Connect to server...")

  - Message "Connecting..." displays in top of dialog box with
spinning
circle for 40 seconds  [shot1.png]

  - After 40 seconds elapsed, error "Timed out when logging in"
displays and connection fails. [shot22.png]

  - On the server side  (log text below)


* On the laptop with Artix I could still open my home drive on the
Manjaro desktop using the same steps that failed to open the FreeBSD as
described.

* I could still use plain-vanilla 'ssh' at the command line without any
problem.

* I could still use SSHFS mounting without any problem.

-----------------

Contents of the server log in FreeBSD for this event:

[/var/log/auth.log]

Mar 24 12:55:11 .... sshd[10445]: user p..... login class  [preauth]
Mar 24 12:55:11 .... syslogd: last message repeated 1 times
Mar 24 12:55:52 .... sshd[10445]: error: PAM: Authentication error for
p..... from x.y.z
Mar 24 12:55:52 .... sshd[10445]: Connection closed by authenticating
user p..... 172.16.0.35 port 33864 [preauth]

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

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

--- Comment #1 from MickeyDee <vintongunker64 at gmail.com> ---
Created attachment 3488
  --> https://bugzilla.mindrot.org/attachment.cgi?id=3488&action=edit
screen shot - Nemo wait screen for 40 seconds

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

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

Darren Tucker <dtucker at dtucker.net> changed:

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

--- Comment #2 from Darren Tucker <dtucker at dtucker.net> ---
(In reply to MickeyDee from comment #0)
[...]
> * I could still use plain-vanilla 'ssh' at the command line without
> any problem.
This means that OpenSSH as supplied (and modified by Arch) still works,
so it's likely a problem with something other than OpenSSH.  There's
not much we can do to diagnose this, so you need to report this to
Arch.

-- 
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=3287

Darren Tucker <dtucker at dtucker.net> changed:

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

--- Comment #3 from Darren Tucker <dtucker at dtucker.net> ---
Closing as there is no evidence of this being something that can be
reproduced with the stock OpenSSH as supplied by the OpenSSH team. 
Please reopen if you can reproduce this with the stock OpenSSH.

-- 
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=3287

Damien Miller <djm at mindrot.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #4 from Damien Miller <djm at mindrot.org> ---
closing bugs resolved before openssh-8.9

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