From owner-freebsd-security Fri Jun 28 7:55:42 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 A5AF037B401 for ; Fri, 28 Jun 2002 07:55:34 -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 3F39743E0F for ; Fri, 28 Jun 2002 07:55:34 -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 17Nx9q-000CUA-00; Fri, 28 Jun 2002 10:55:34 -0400 Received: from scott by bsd.smnolde.com with local (Exim 3.33 #1) id 17Nx9p-0008mw-00; Fri, 28 Jun 2002 10:55:33 -0400 Date: Fri, 28 Jun 2002 10:55:33 -0400 From: "Scott M. Nolde" To: Roger 'Rocky' Vetterberg Cc: freebsd-security@FreeBSD.ORG Subject: Re: More OpenSSH weirdness Message-ID: <20020628105533.C19461@smnolde.com> References: <20020628101235.A19461@smnolde.com> <20020628101512.B19461@smnolde.com> <3D1C7878.5010907@rambo.simx.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3D1C7878.5010907@rambo.simx.org>; from listsub@rambo.simx.org on Fri, Jun 28, 2002 at 04:53:44PM +0200 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 Hey Rocky, Quite possibly, but this didn't happen for previous versions of OpenSSH. And I'm still dealing with the compression issue with privsep enabled. - Scott Roger 'Rocky' Vetterberg(listsub@rambo.simx.org)@2002.06.28 16:53:44 +0000: > Scott M. Nolde wrote: > > Scott M. Nolde(scott@smnolde.com)@2002.06.28 10:12:35 +0000: > > > >>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? > >> > > > > > > A new cvsup is underway to fix the compression issue with 3.4p1_1, but has > > anyone else seen sshd miss .profile? > > > > Correct me if Im wrong, but .profile is read by the shell that > sshd starts, not by sshd itself, right? > > Hi Scott btw :) > -- Scott Nolde GPG Key 0xD869AB48 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message