From owner-freebsd-security  Fri Apr 13  9:47:41 2001
Delivered-To: freebsd-security@freebsd.org
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
	by hub.freebsd.org (Postfix) with ESMTP id 4BE3B37B50E
	for <security@FreeBSD.ORG>; Fri, 13 Apr 2001 09:47:38 -0700 (PDT)
	(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id MAA60805;
	Fri, 13 Apr 2001 12:47:27 -0400 (EDT)
	(envelope-from wollman)
Date: Fri, 13 Apr 2001 12:47:27 -0400 (EDT)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <200104131647.MAA60805@khavrinen.lcs.mit.edu>
To: Mikhail Kruk <meshko@cs.brandeis.edu>
Cc: <security@FreeBSD.ORG>
Subject: Re: SSHD
In-Reply-To: <Pine.LNX.4.30.0104131239180.13954-100000@calliope.cs.brandeis.edu>
References: <3AD72A8A.50B71BF@gmx.net>
	<Pine.LNX.4.30.0104131239180.13954-100000@calliope.cs.brandeis.edu>
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

<<On Fri, 13 Apr 2001 12:41:12 -0400 (EDT), Mikhail Kruk <meshko@cs.brandeis.edu> said:

> I can't give you a good advice on how to fix 4.1
> You may want to try upgrading the whole ports tree, but that won't
> probably work.

The ports system works, with some exceptions, on systems as old as
3.4.  It is necessary to make a few minor changes in Mk/bsd.port.mk in
order for this to work, but beyond that most stand-alone program ports
work just fine, so long as the code actually supports old systems.
(That's precisely what I did with sshd on one of my 3.4 systems and a
couple of old 5-current systems a few months ago.)

-GAWollman


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message