From owner-freebsd-security@freebsd.org Mon Jan 30 22:52:21 2017 Return-Path: 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 9FC43CC8054 for ; Mon, 30 Jan 2017 22:52:21 +0000 (UTC) (envelope-from jungleboogie0@gmail.com) Received: from mail-it0-x22d.google.com (mail-it0-x22d.google.com [IPv6:2607:f8b0:4001:c0b::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 67E0E1E38 for ; Mon, 30 Jan 2017 22:52:21 +0000 (UTC) (envelope-from jungleboogie0@gmail.com) Received: by mail-it0-x22d.google.com with SMTP id c7so204446279itd.1 for ; Mon, 30 Jan 2017 14:52:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=UjOtX/Hwr8yFyEQIYZF30O9Nvvd//qAMOn958XSxbi0=; b=t9TQGWSoa7gXrdVJy86yCG7R/VZRWtZ0jW5ni8qKwuBgLzpbQ+P+AwgsZwqvKt9LR2 GufC4nzSw4aozTAyFkcRwFKIXu/lkaa5IcQotin0M/GkuVcivOURVHvJ81PkidwxyoQe B89iU4jjWp9Pudz0nt9cTU3x3B1MFqC5h95BFZCq/81bGBPfZz+cAaJwMYEGul6UIuH8 4v+nYUCoML0UUCHo/SHb2FfWDgrFMu3hhbai7D+lq/Y2vfFvXPHd/0KtIPvbB0uTffD6 x2hNWPpWeYJEl+2p/o/J14ctCV8EhJM9Z6Gphh52W+CoDgJnrDcYtfF57G5KTkxdj+fR KBcQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=UjOtX/Hwr8yFyEQIYZF30O9Nvvd//qAMOn958XSxbi0=; b=HLetUBZ+hN/FbBk/cnggijqYLIhPVf9P0bdZAX+MyyWnGQ8ODB/3jNJ9+7p5AI5eOv 01B+9ESyI19uEQzC0+RES5qIAN5GEpjzcb+fLUsWRC/KOXga5l6prOkR2Zs181nhaUEt cfNlz0X+PFULdtVP5w20J/udzKE39+Hk95GZ2QWlozF6XagW/Vh4D3Hj32lbh4g6idDn nciNkQ+uki2OukhHePTnj75zGdL7hSeKZmoF0SvOyebee5e+94KLykp5IJF/k/KIv2QX FxV//F5dBmCr6WKP2Z0+sB/Szq5kFgWwlFD/uHqaRCVKkLjPgvleEWaG3nZ4nijBN3h9 19Mw== X-Gm-Message-State: AIkVDXKPinKF0IYKkRfOhUHnhyxGP/4KYn3/CujwL12QqdDujjTep1FNCBJ8PX32/x+jICdHcHUuSOeCIRjOsA== X-Received: by 10.36.62.133 with SMTP id s127mr18284125its.110.1485816740824; Mon, 30 Jan 2017 14:52:20 -0800 (PST) MIME-Version: 1.0 Received: by 10.36.142.199 with HTTP; Mon, 30 Jan 2017 14:52:20 -0800 (PST) In-Reply-To: <20170130222443.GL73060@shrubbery.net> References: <20170127173016.GF12175@shrubbery.net> <867f5c66yr.fsf@desk.des.no> <20170130195226.GD73060@shrubbery.net> <20170130222443.GL73060@shrubbery.net> From: jungle Boogie Date: Mon, 30 Jan 2017 14:52:20 -0800 Message-ID: Subject: Re: fbsd11 & sshv1 To: heasley Cc: =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= , freebsd-security@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jan 2017 22:52:21 -0000 On 30 January 2017 at 14:24, heasley wrote: > Mon, Jan 30, 2017 at 01:56:03PM -0800, jungle Boogie: >> On 30 January 2017 at 11:52, heasley wrote: >> > Mon, Jan 30, 2017 at 01:57:32PM +0100, Dag-Erling Sm=C3=B8rgrav: >> >> heasley writes: >> >> > So, what is the BCP to support a v1 client for outbound connections= on fbsd >> >> > 11? Hopefully one that I do not need to maintain by building a spe= cial ssh >> >> > from ports. Is there a pkg that I'm missing? >> >> >> >> 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 w= ill >> >> have to find some other SSH client. >> > >> > That is sad; I doubt that I am the only one who would need this - ther= e >> > are millions of Cisco, HP, and etc network devices that folks must con= tinue >> > to access but will never receive new firmware with sshv2. It takes a = long >> > time for some equipment to transition to the recycle bin - even after >> > vendor EOLs. >> >> Well you have about 7 months until it's deprecated from openssh. >> What's wrong with continuing to use openSSH 7.4 post sshv1 >> deprecation? > > whats wrong with providing a 7.4+v1 port for everyone to use? What will happen when 7.4 gets a vulnerability, then? I don't think you or I will be patching it (or anyone else) and therefore, the port/pkg will be knowingly vulnerable. Why do we want that? --=20 ------- inum: 883510009027723 sip: jungleboogie@sip2sip.info