From owner-freebsd-security Sun Mar 31 6:13:26 2002 Delivered-To: freebsd-security@freebsd.org Received: from roc-66-66-72-6.rochester.rr.com (roc-66-66-72-6.rochester.rr.com [66.66.72.6]) by hub.freebsd.org (Postfix) with ESMTP id 27CFE37B41A for ; Sun, 31 Mar 2002 06:13:23 -0800 (PST) Received: by roc-66-66-72-6.rochester.rr.com (Postfix, from userid 1000) id E02F7901A00; Sun, 31 Mar 2002 09:12:02 -0500 (EST) Date: Sun, 31 Mar 2002 09:12:02 -0500 From: mpd To: Jesper Wallin Cc: security@freebsd.org Subject: Re: Why update the world because of OpenSSH? Message-ID: <20020331091202.A91049@rochester.rr.com> References: <4487.213.112.58.135.1017583220.squirrel@phucking.kicks-ass.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: <4487.213.112.58.135.1017583220.squirrel@phucking.kicks-ass.org>; from z3l3zt@phucking.kicks-ass.org on Sun, Mar 31, 2002 at 04:00:20PM +0200 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 On Sun, Mar 31, 2002 at 04:00:20PM +0200, Jesper Wallin wrote: > Once again I make me look like a fool.. > > I'm quite new to both mailinglists and FreeBSD so I'm not sure IF i should > post this or where I should post if.. sorry for pissing you off.. > > Well, for some month ago I saw the warnings about the root exploit for > OpenSSH here. What I never understood what, why should I update my world > because of an OpenSSH exploit? Isn't it enought to just cvsup the ports and > re-install OpenSSH from the ports? OpenSSH is part of the base system in both -STABLE and -CURRENT, and has been for awhile now. > > > //Jesper aka Z3l3zT > mike -- ___________________________________________________________ "WITH A FEW SMALL MODIFICATIONS ANY CANOE CAN TRAVEL THROUGH TIME!!!" - Pokey the Penguin from "POKEY IN ANCIENT SCOTLAND" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message