From owner-freebsd-security@freebsd.org  Fri Feb  3 04:13:59 2017
Return-Path: <owner-freebsd-security@freebsd.org>
Delivered-To: freebsd-security@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4FECCCCD102
 for <freebsd-security@mailman.ysv.freebsd.org>;
 Fri,  3 Feb 2017 04:13:59 +0000 (UTC)
 (envelope-from smithi@nimnet.asn.au)
Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id C12AAF29
 for <freebsd-security@freebsd.org>; Fri,  3 Feb 2017 04:13:57 +0000 (UTC)
 (envelope-from smithi@nimnet.asn.au)
Received: from localhost (localhost [127.0.0.1])
 by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id v134Di8U032745;
 Fri, 3 Feb 2017 15:13:45 +1100 (EST)
 (envelope-from smithi@nimnet.asn.au)
Date: Fri, 3 Feb 2017 15:13:44 +1100 (EST)
From: Ian Smith <smithi@nimnet.asn.au>
To: heasley <heas@shrubbery.net>
cc: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= <des@des.no>,
 freebsd-security@freebsd.org
Subject: Re: fbsd11 & sshv1
In-Reply-To: <20170203005331.GG8381@shrubbery.net>
Message-ID: <20170203143417.C33334@sola.nimnet.asn.au>
References: <20170127173016.GF12175@shrubbery.net> <867f5c66yr.fsf@desk.des.no>
 <20170130195226.GD73060@shrubbery.net> <867f5bfmde.fsf@desk.des.no>
 <20170131201722.GH11924@shrubbery.net> <86y3xqdxox.fsf@desk.des.no>
 <20170203005331.GG8381@shrubbery.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security/>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 04:13:59 -0000

On Fri, 3 Feb 2017 00:53:31 +0000, heasley wrote:
 > Wed, Feb 01, 2017 at 11:15:10AM +0100, Dag-Erling Smørgrav:
 > > > 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.
 > > 
 > > You mean like net/tcpdump398, which was forked from net/tcpdump because
 > > some people liked its output format better than that of tcpdump 4, and
 > > then forgotten, and is known to have dozens of security vulnerabilities?
 > 
 > I dont care what they do.  They are consenting adults and could be told
 > that the port is EoS and may have holes.  seems like a different animal
 > though; this isnt for fashion.  I've transitioned everything that can be
 > to sshv2, what remains is stuck in time.

Nobody 'forbids' you from making such a port, for your own use and/or 
for others.  See Peter Jeremy's suggestion re where it might be placed 
and what sort of dire warnings it ought to announce; I expect SO and 
ports secteam would insist on nothing less.

This differs from expecting|demanding|hoping somebody ELSE should do it.

Anyway, you've got lots of time until FreeBSD 10 is no longer supported.

cheers, Ian