From owner-freebsd-security Thu Jun 27 12:38:26 2002 Delivered-To: freebsd-security@freebsd.org Received: from mail.fibertel.com.ar (mta3.fibertel.com.ar [24.232.0.163]) by hub.freebsd.org (Postfix) with ESMTP id 88E8037B407; Thu, 27 Jun 2002 12:38:05 -0700 (PDT) Received: from juan (24.232.67.221) by mail.fibertel.com.ar (5.5.034) id 3D19BD4900065552; Thu, 27 Jun 2002 16:36:18 -0300 Date: Thu, 27 Jun 2002 16:39:46 -0300 From: "JP Villa (Datafull.com)" X-Mailer: The Bat! (v1.60m) Reply-To: "JP Villa (Datafull.com)" X-Priority: 3 (Normal) Message-ID: <41256714305.20020627163946@datafull.com> To: owner-freebsd-security@FreeBSD.ORG, Dag-Erling Smorgrav Cc: freebsd-security@FreeBSD.ORG Subject: Re[2]: openssh OR openssh-portable In-Reply-To: References: <3D1AD7C4.9020909@cerint.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Taking a look at the handbook, it's pretty clear that -STABLE is not an option for production boxes. Personally, I prefer to stick with RELENG_4_6 because of this. Then, the question is: What do I have to do with OpenSSH? (don't tell me 2.9, I want the latest codebase possible) The platform integration is not an issue for me right now, as I just want the basic functionality and get some good sleep. I think the original question was pointing to this too, so I rephrase: openssh or openssh-portable? or maybe openssh 3.4 properly merged on a production codebase? and in that case, when? Best regards, Juan Pablo Villa DATAFULL.COM Sysadmin Cuatro Cabezas S.A. Buenos Aires, Argentina Thursday, June 27, 2002, 9:29:29 AM, you wrote: DES> Marcin Gryszkalis writes: >> Which port should I use (I'm migrating from -stable basesystem ssh) DES> Neither. Calm down and wait for 3.4p1 to hit -STABLE. DES> DES To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message