From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 24 05:35:35 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 901DA37B401 for ; Tue, 24 Jun 2003 05:35:35 -0700 (PDT) Received: from comp.chem.msu.su (comp-ext.chem.msu.su [158.250.32.157]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F8CD43FE9 for ; Tue, 24 Jun 2003 05:35:34 -0700 (PDT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.12.3p2/8.12.3) with ESMTP id h5OCZVpV046488; Tue, 24 Jun 2003 16:35:31 +0400 (MSD) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.12.3p2/8.12.3/Submit) id h5OCZVrd046487; Tue, 24 Jun 2003 16:35:31 +0400 (MSD) (envelope-from yar) Date: Tue, 24 Jun 2003 16:35:30 +0400 From: Yar Tikhiy To: Socketd Message-ID: <20030624123530.GA44556@comp.chem.msu.su> References: <20030621202739.35446e75.db@traceroute.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030621202739.35446e75.db@traceroute.dk> User-Agent: Mutt/1.5.3i cc: hackers@freebsd.org Subject: Re: Ftpd (option -h not working) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2003 12:35:35 -0000 On Sat, Jun 21, 2003 at 08:27:39PM +0200, Socketd wrote: > > When FreeBSD 4.8 was released I reported this bug, but now in 5.1 > releaed it is still there. Since http://www.freebsd.org/send-pr.html is > "down" I'll try reporting the bug here (again). Please use the send-pr(1) utility to submit your bug reports. > When using ftpd, you have the -h option to prevent the server from > giving any info about itself. This works fino regarding the greeting > message and when typing "stat", but with "syst" is still gives info to > the user. Thanks for reporting. I've already fixed this minor bug in both CURRENT and STABLE branches. -- Yar