Date: Sun, 11 Feb 2001 16:30:52 -0500 From: Peter Radcliffe <pir@pir.net> To: freebsd-security@FreeBSD.ORG Subject: Re: Default sshd_config settings Message-ID: <20010211163052.D8149@pir.net> In-Reply-To: <20010211131638.B79776@mollari.cthul.hu>; from kris@obsecurity.org on Sun, Feb 11, 2001 at 01:16:38PM -0800 References: <000701c0945c$eb3eaff0$0300a8c0@magus> <20010211121803.A78601@mollari.cthul.hu> <20010211124834.T3274@fw.wintelcom.net> <20010211124958.A79375@mollari.cthul.hu> <20010211130149.U3274@fw.wintelcom.net> <20010211131638.B79776@mollari.cthul.hu>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway <kris@obsecurity.org> probably said: > On Sun, Feb 11, 2001 at 01:01:49PM -0800, Alfred Perlstein wrote: > > Is this new in 2.3.0 (time to update the port then?) It seems to > > all work now. :) > > Good to hear it works. Last I heard, Brian doesn't intend to update > the port because it's not useful to the 4.x branch. If you wanted to > take over maintainership and provide support for older releases I'm > sure he'll be willing. My experiments with 2.3.0p1 have shown that the agent works with V2 connections but agent forwarding does not. Agent forwarding is all that is stopping me from going completly sshV2. Someone in -stable mentioned that this was a known bug (and the ChangeLog for openssh agrees) and that it is fixed in a development version but not in a real release. Hopefully full 2.3.1 or 2.3.2 (if they don't release 2.3.1 due to the security problem in the development version) will have this fixed. P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010211163052.D8149>