From owner-freebsd-stable Mon Mar 19 0:12:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 7288037B719 for ; Mon, 19 Mar 2001 00:12:23 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f2J8CAp04946; Mon, 19 Mar 2001 00:12:10 -0800 (PST) (envelope-from dillon) Date: Mon, 19 Mar 2001 00:12:10 -0800 (PST) From: Matt Dillon Message-Id: <200103190812.f2J8CAp04946@earth.backplane.com> To: Jonathan Lemon Cc: stable@freebsd.org Subject: Re: Not only ftpd's problem with ls */../*..... References: <200103172253.f2HMrZ008412@prism.flugsvamp.com> <200103180027.f2I0RSn96769@earth.backplane.com> <20010317222918.B82645@prism.flugsvamp.com> <200103180543.f2I5hb398084@earth.backplane.com> <20010318160034.F82645@prism.flugsvamp.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, it's better then nothing I suppose but it doesn't really solve the ftpd DOS attack (nor does the original patch). Long paths can still result in a DOS. The limit should probably be specified in bytes rather then entries. That would solve the problem neatly. Whatever happens, the release can't go out with the current patch in place. Even an incomplete patch which defaults to 'off' is better then a broken patch which defaults to 'on'. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message