I have just updated to MacOS Sierra, and found that openssh version 1 has beed disabled or removed.
ssh1 is not supported
I have to use ssh1 for some server, how can I enable ssh1?
Or can I install another openssh which support ssh1 tentatively?
Ask Different is a question and answer site for power users of Apple hardware and software. It only takes a minute to sign up.Sign up to join this community
Here's my github repo trying to solve the problem by patching the openssh in homebrew/dupes. It's far from perfect but works.
Basically you have to:
brew tap homebrew/dupes curl -fsSL https://github.com/boltomli/MyMacScripts/raw/master/homebrew/homebrew-dupes.openssh.diff | patch /usr/local/Homebrew/Library/Taps/homebrew/homebrew-dupes/openssh.rb brew install openssh --with-ssh1
curl/patch line from above slightly modified to run on macOS Sierra...
curl -fsSL https://github.com/boltomli/MyMacScripts/raw/master/homebrew/homebrew-dupes.openssh.diff | patch /usr/local/Library/Taps/homebrew/homebrew-dupes/openssh.rb
openSSH has been moved from 'dupes' to 'core'. boltomli has updated his GitHub repo to account for this. Here is the new command to get it working on Sierra.
curl -fsSL https://raw.githubusercontent.com/boltomli/MyMacScripts/master/homebrew/homebrew-core.openssh.diff | patch /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core/Formula/openssh.rb brew install openssh --with-ssh1
Given that ssh1 is absolutely ancient (v2 has been standard for 10 years now) a far better solution is upgrading the security on the server you access that is still running ssh1 only. V1 has all the usual security issues of 20 year old software, whoever is managing that particular piece of hardware is simply not doing their job.
You can probably install an alternate client that supports V1, but I would send a memo to management that they have a major issue with their legacy hardware.