Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 31 Jan 2017 13:24:29 +0100
From:      =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no>
To:        heasley <heas@shrubbery.net>
Cc:        freebsd-security@freebsd.org
Subject:   Re: fbsd11 & sshv1
Message-ID:  <867f5bfmde.fsf@desk.des.no>
In-Reply-To: <20170130195226.GD73060@shrubbery.net> (heasley's message of "Mon, 30 Jan 2017 19:52:26 %2B0000")
References:  <20170127173016.GF12175@shrubbery.net> <867f5c66yr.fsf@desk.des.no> <20170130195226.GD73060@shrubbery.net>

next in thread | previous in thread | raw e-mail | index | archive | help
heasley <heas@shrubbery.net> writes:
> Dag-Erling Sm=C3=B8rgrav <des@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.

DES
--=20
Dag-Erling Sm=C3=B8rgrav - des@des.no



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?867f5bfmde.fsf>