Date: Tue, 19 Nov 2002 11:08:37 +0200 (EET) From: Dmitry Cherkasov <chd@intercom.net.ua> To: FreeBSD-gnats-submit@FreeBSD.org Subject: bin/45472: ftphosts causes ftpd failure Message-ID: <200211190908.gAJ98bwH017918@fortress.intercom.net.ua>
next in thread | raw e-mail | index | archive | help
>Number: 45472 >Category: bin >Synopsis: ftphosts causes ftpd failure >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Nov 19 01:10:02 PST 2002 >Closed-Date: >Last-Modified: >Originator: Dmitry Cherkasov >Release: FreeBSD 4.7-RELEASE-p2 i386 >Organization: ISP Intercom >Environment: System: FreeBSD fortress.intercom.net.ua 4.7-RELEASE-p2 FreeBSD 4.7-RELEASE-p2 #0: Mon Nov 18 21:14:12 EET 2002 chd@fortress.intercom.net.ua:/usr/src/sys/compile/Fortress i386 >Description: If any not empty file /etc/ftphosts is present, and hostname is not 127.0.0.1 or localhost, ftpd dumps core. If /etc/ftphosts is empty or absent, ftpd operates normally. No any dependance upon ftpd or inetd command-line options or /etc/hosts.allow contents have been noticed. >How-To-Repeat: 1) build FreeBSD 4.7-RELEASE-p2 i386 2) allow starting ftpd in /etc/inetd.conf, (re)start inetd 3) remove /etc/ftphosts if it is present 4) connect to ftp port, for example: ftp <your-IP-address> see that there are no problems 5) create /etc/ftphosts with any not empty contents according to ftpd(8), for example: <your-IP-address> ftp 6) connect to ftpd -- see that service is not available 7) substitude the contents in /etc/ftphosts with th following line: 127.0.0.1 ftp see ftpd operating normally again. >Fix: Workaround: downgrade to 4.7-RELEASE-p1 >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200211190908.gAJ98bwH017918>