From owner-freebsd-stable@FreeBSD.ORG Thu Jun 20 00:15:25 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 83ECC64F for ; Thu, 20 Jun 2013 00:15:25 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) by mx1.freebsd.org (Postfix) with ESMTP id 45AE21982 for ; Thu, 20 Jun 2013 00:15:25 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 7162C2842F; Thu, 20 Jun 2013 02:15:24 +0200 (CEST) Received: from [192.168.1.2] (ip-89-177-49-222.net.upcbroadband.cz [89.177.49.222]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 9735A2842B; Thu, 20 Jun 2013 02:15:23 +0200 (CEST) Message-ID: <51C2499B.2060209@quip.cz> Date: Thu, 20 Jun 2013 02:15:23 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.19) Gecko/20110420 Lightning/1.0b1 SeaMonkey/2.0.14 MIME-Version: 1.0 To: Kimmo Paasiala Subject: Re: sshd didn't run after upgrade to FreeBSD 8.4 References: <51C22E11.3020008@quip.cz> <51C23ED9.7070107@quip.cz> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable Stable , Steven Hartland X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jun 2013 00:15:25 -0000 Kimmo Paasiala wrote: > On Thu, Jun 20, 2013 at 2:40 AM, Steven Hartland > wrote: >> >> >> I believe Miroslav is saying he left his old but previously working >> sshd_config as was when updating, so its a change to the code which >> now fails on an empty VersionAddendum, where it previously didn't >> hence the problem. Yes, this is my point - I left my old and previously working sshd_config with empty VersionAddendum. > Err yes, your right. The proper way to specify empty VersionAddendum > based on some googling seems to be now: > > > VersionAddendum "" This is not true, it will add two quotes to the banner: SSH-2.0-OpenSSH_6.1_hpn13v11 "" Default banner (no VersionAddendum in sshd_config): SSH-2.0-OpenSSH_6.1_hpn13v11 FreeBSD-20120901 So I am fine with: VersionAddendum - It will print: SSH-2.0-OpenSSH_6.1_hpn13v11 - I don't need really empty addendum, I just don't want to show FreeBSD version info and empty VersionAddendum was working for me many years. Now it breaks sshd after final reboot on two of our upgraded servers. So Release Notes or better UPDATING entry will warn other users before the same mistake. Thanks to the remote management / KVM on Sun Fire and Supermicro servers that I didn't need to drive to the datacenter and I can fix it remotely. Miroslav Lachman