From owner-freebsd-security Fri Jun 28 7:12:47 2002 Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E400037B400 for ; Fri, 28 Jun 2002 07:12:38 -0700 (PDT) Received: from smnolde.com (c-24-98-61-182.atl.client2.attbi.com [24.98.61.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8173643E0F for ; Fri, 28 Jun 2002 07:12:36 -0700 (PDT) (envelope-from scott@smnolde.com) Received: from [192.168.10.7] (helo=bsd.smnolde.com) by smnolde.com with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 3.36 #1) id 17NwUG-000CDc-00 for freebsd-security@freebsd.org; Fri, 28 Jun 2002 10:12:36 -0400 Received: from scott by bsd.smnolde.com with local (Exim 3.33 #1) id 17NwUF-00056J-00 for freebsd-security@freebsd.org; Fri, 28 Jun 2002 10:12:35 -0400 Date: Fri, 28 Jun 2002 10:12:35 -0400 From: "Scott M. Nolde" To: freebsd-security@freebsd.org Subject: More OpenSSH weirdness Message-ID: <20020628101235.A19461@smnolde.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-GPG_Fingerprint: 0BD6 DDB4 2978 EB60 E0C8 33F2 BC34 9087 D869 AB48 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org After installing openssh-portable 3.4p1 last night on my 4.6-STABLE systems I noticed two problems immediately: 1. Using compression with ssh would give the error: no matching comp found: client zlib server none 2. After I was able to log into the machine with a new ssh process sshd did not read $/.profile and some PATH stuff was left out. The workaround for (1) was to disable compression. But having (2) happen was very odd. Does anyone have any suggestions for this? I find it quite disturbing to upgrade from 3.3p1 to 3.4p1 and have things break like this. Any particular things I should watch out for? -- Scott Nolde GPG Key 0xD869AB48 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message