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

[MacPorts]

#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:16 ryandesign]:
 > Replying to [comment:10 fhgwright]:
 > > And since the mechanism for automatically reloading a previously
 loaded port after a deactivate/activate is extremely unreliable,
 >
 > This is the first I've heard of that. If there is not already a bug
 report, please file one.

 I'm afraid I'm another one who was blindsided by the change to `openssh` .
 I'm in the middle of a multiple-level disaster of my own which started
 with the internal SSD on my Mac going haywire.  Once I got things back to
 where they had been on July 1st, I thought I'd update my ports
 (''partially because I didn't trust some aspects of the Time Machine
 restore'').  I updated `openssh`, and then updated some other port which
 did run into a problem which was due to the Time Machine restore.  Ie, it
 was not caused by anything in MacPorts.  Due to **that**, I cleaned out
 all deactivated ports, including the deactivated version of `openssh`
 which was left over due to the install I had done just a few minutes
 earlier.

 Okay, so after more pain, I get most ports upgraded.  I then went to `ssh`
 to a machine which happens to need one of the key-types which had been
 removed.  I hit the errors, and **Ugh**.  Okay, I'll just re-install the
 version of `openssh` which had been installed before today.  As near as I
 can tell, it is not possible to install the older version.  I'm told that
 it's not available.  And I don't even have the option to just `activate`
 the previous version, because I had to clean out the non-active versions
 of other ports due to an unrelated issue.  Is there any version I can
 install which will still support the now-unsupported keys?

 Am I just stuck?  I understand that everyone involved is trying to "Do the
 Right Thing", but it leaves me with many servers that I cannot access.  I
 know there are ways I can get around this by bouncing through other
 servers of mine, but that's going to get pretty painful.

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