On 1/31/2017 3:17 PM, heasley wrote:
Tue, Jan 31, 2017 at 01:24:29PM +0100, Dag-Erling Smørgrav:
heasley <h...@shrubbery.net> writes:
Dag-Erling Smørgrav <d...@des.no> writes:
FreeBSD 10 supports SSHv1 and will continue to do so. FreeBSD 11
and 12 do not, and neither does the openssh-portable port. I'm
afraid you will have to find some other SSH client.
That is sad;
You know what would be even sadder? If the OpenSSH developers had to
continue to devote significant resources to maintaining a rat's nest of
legacy code so 0.0001% of their users could continue to use an obsolete
protocol to connect to obsolete equipment, instead of devoting those
same resources to developing new features and improving existing ones.
Especially when those users have plenty of alternatives to choose from,
including but not limited to security/putty.
I was not suggesting that openssl maintain their apparently messy code;
they're maintaining it already, for whatever the remaining period is.
i'm suggesting a port with a v1 client; that is built with all the other
binary ports for abi changes and whatever else is reasonable. yes, i
can build my own, but i feel it should be a port.
I appreciate the putty suggestion, but it appears to be graphical only.
Happy to have it pointed-out that I've missed a port having v1.
i also understand the devote position of buy new equipment to advance
security; its simply not going to happen anytime soon. and i'm not alone.
i'm not rich, i don't crontrol depreciation schedules, etc etc.
_______________________________________________
freebsd-security@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-security
To unsubscribe, send any mail to "freebsd-security-unsubscr...@freebsd.org"
There is a non-graphical port of putty (putty-nogtk) which installs plink
_______________________________________________
freebsd-security@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-security
To unsubscribe, send any mail to "freebsd-security-unsubscr...@freebsd.org"
