From owner-freebsd-questions@freebsd.org Tue Mar 8 16:27:03 2016 Return-Path: Delivered-To: freebsd-questions@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 E47CCAC822A for ; Tue, 8 Mar 2016 16:27:03 +0000 (UTC) (envelope-from dan@buildingonline.com) Received: from alisocreek.buildingonline.net (alisocreek.buildingonline.net [204.109.62.198]) by mx1.freebsd.org (Postfix) with ESMTP id CBE2C7C2 for ; Tue, 8 Mar 2016 16:27:03 +0000 (UTC) (envelope-from dan@buildingonline.com) Received: by alisocreek.buildingonline.net (Postfix, from userid 58) id D285D992A98; Tue, 8 Mar 2016 08:20:33 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on alisocreek.buildingonline.net X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.0 Received: from Whistler.local (unknown [69.51.79.5]) (Authenticated sender: dan@dpcsys.com) by alisocreek.buildingonline.net (Postfix) with ESMTPA id 947EC991B23 for ; Tue, 8 Mar 2016 08:20:32 -0800 (PST) Subject: Re: freebsd-update just broke ssh. How do I fix this? To: freebsd-questions@freebsd.org References: <56DDD3D8.8040604@gmail.com> From: Dan Busarow Organization: BuildingOnline.com Message-ID: <56DEFBCF.8050305@buildingonline.com> Date: Tue, 8 Mar 2016 09:20:31 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Mar 2016 16:27:04 -0000 On 3/7/16 5:39 PM, William Dudley wrote: > In answer to my own question: > > 1. a bug has been filed (by someone else): > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207783 > > 2. sudo freebsd-update rollback restores the old openssh, which > has security problems, but "works". I just want to confirm Bill's report. I had seen his post yesterday and when I got the notice that there was an update this morning I held off upding all of my boxes. I tested by running freebsd-update install on a 9.3-RELEASEp33 system. After completing the install I could no longer ssh into the box. I tried rebooting just in case but that did not help. As Bill said, freebsd-update rollback got the old ssh reinstalled and I'm able to ssh into the box again. Dan > > Bill Dudley > > > This email is free of malware because I run Linux. > > On Mon, Mar 7, 2016 at 2:17 PM, William F. Dudley Jr. > wrote: > >> I did a freebsd-update fetch and install on a 9.3 system, and it replaced >> all the openssh stuff with >> new stuff. Now ssh is totally broken. (core dump when attempting to ssh >> out, ssh in gets "connection >> closed". Now what? >> >> uname -a >> FreeBSD dudley 9.3-RELEASE-p33 FreeBSD 9.3-RELEASE-p33 #0: Thu Jan 14 >> 00:48:15 UTC 2016 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC >> i386 >> >> ssh -V >> OpenSSH_6.6.1p1, OpenSSL 0.9.8zh-freebsd 3 Dec 2015 >> >> ssh django >> Memory fault (core dumped) >> >> which ssh >> /usr/bin/ssh >> >> Thanks, >> Bill Dudley >> >> > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >