[MacPorts] #70319: openssh @9.8p1 broke some key types

MacPorts noreply at macports.org
Mon Jul 15 03:15:05 UTC 2024


#70319: openssh @9.8p1 broke some key types
------------------------+----------------------
  Reporter:  fhgwright  |      Owner:  artkiver
      Type:  defect     |     Status:  assigned
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.9.3
Resolution:             |   Keywords:
      Port:  openssh    |
------------------------+----------------------

Comment (by drosehn):

 Replying to [comment:21 danielluke]:
 > Replying to [comment:18 drosehn]:
 > > I'm afraid I'm another one who was blindsided by the change to
 `openssh` .
 >
 > "blindsided" by forgetting that you made a config change in 2015 where
 the instructions warned you that this day was coming but you didn't
 migrate to some other key type...

 "Blindsided" in that the desktop computer I use in my office died with
 hardware errors on July 5th.  "Blindsided" in the sense that I got a fixed
 computer after 5pm on Friday July 12th (in a week I was scheduled to be on
 vacation), and it would be awfully nice if that computer was mostly-
 working by 10am on Monday morning.  "Blindsided" in that after spending
 over an hour doing a full restore of the dead SSD onto the new SSD, there
 were a few minor issues which weren't working right.  Most things were
 working fine, but there were a few minor annoyances.  "Blindsided" in that
 while trying to fix those minor annoyances I decided to upgrade macports.
 This did indeed did fix one or two **minor** issues but also resulted in
 what was a much more serious issue for me.  "Blindsided" in that by the
 time I realized the new `ssh` had broken things for me, it was already
 past 2am on Saturday.  That kind of "Blindsided".

 Also, the feature I'm using is the one which was deprecated in 2021
 (during Covid) in `OpenSSH 8.8/8.8p1 (2021-09-26)`, not back in 2015.   In
 2021 and 2022 I had several more important issues to worry about than an
 option in `.ssh/config` (including issues that I'm not going to describe
 here).

 And some added irony is that one of the projects I need to work on this
 week will hopefully let us unplug some of these very same out-of-date
 servers before Sept 1st (possibly before Aug 1st?).  But oddly enough I
 need to `ssh` **into** those servers to complete that project.

 ___
 >
 > > As near as I can tell, it is not possible to install the older
 version.
 >
 > https://trac.macports.org/wiki/howto/InstallingOlderPort

 Thanks.  This part is very helpful.  It has been many years since I've had
 any significant issue with Macports, so I was totally unaware of the
 options which are currently available.  I'm pretty sure that the last time
 I had a significant problem, Macports wasn't even in github!  I ended up
 going with a different solution, but it's nice to realize that a solution
 such as this is available.

-- 
Ticket URL: <https://trac.macports.org/ticket/70319#comment:22>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list