Date: Fri, 3 Feb 2017 17:04:52 +0000 From: heasley <heas@shrubbery.net> To: Ian Smith <smithi@nimnet.asn.au> Cc: freebsd-security@freebsd.org Subject: Re: fbsd11 & sshv1 Message-ID: <20170203170452.GA40078@shrubbery.net> In-Reply-To: <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> <20170203143417.C33334@sola.nimnet.asn.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Fri, Feb 03, 2017 at 03:13:44PM +1100, Ian Smith: > 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. i've already explained why I think we (as in those needing it) building our own is a worse security approach. Its also a bit silly for all those folks to do it themselves; for the same reason that there are binary ports. i'll need to modify some code, but i'll try plink instead of maintaining my own. until then, i've built my own v1 openssh client.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170203170452.GA40078>