From owner-freebsd-ports Thu Jun 15 12:27:16 2000 Delivered-To: freebsd-ports@freebsd.org Received: from apoq.skynet.be (apoq.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id E4C4D37BC8B for ; Thu, 15 Jun 2000 12:27:10 -0700 (PDT) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by apoq.skynet.be (Postfix) with ESMTP id 6C9F41F414 for ; Thu, 15 Jun 2000 21:27:06 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: Date: Thu, 15 Jun 2000 21:26:24 +0200 To: ports@freebsd.org From: Brad Knowles Subject: Problems with spegla? Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Folks, I'm in the process of setting up another mirror server (to temporarily take the place of our current one, while I rebuild it), and I'm using FreeBSD 4.0-STABLE and spegla to do it. However, I've run into some problems where at least two sites (ftp.blizzard.com and ftp.fr.vapor.com/ftp.us.vapor.com) don't recognize "list ." as valid syntax. Note that it would appear that both of these machines are running on some sort of NT box, according to queso (1.20 1998/09/22) & nmap (2.3BETA14), while the ftp daemon on the former is "blz-ftp Microsoft FTP Service (Version 4.0)", and the latter is running "WarFTPd 1.70.b01.04" (although it claims "Remote system type is UNIX"). Has anyone else run into this? Is there a way I can solve this from within spegla, or do I have to set up an alternate www-based mirroring system for these two sites? Thanks! PS As an interesting side-note, I looked at what TCP & UDP ports are open on these machines: $ nmap -sT ftp.fr.vapor.com Starting nmap V. 2.3BETA14 by fyodor@insecure.org ( www.insecure.org/nmap/ ) Interesting ports on barney.umassmed.edu (146.189.121.87): Port State Protocol Service 21 open tcp ftp 23 open tcp telnet 80 open tcp http 135 filtered tcp loc-srv 139 filtered tcp netbios-ssn $ nmap -sU ftp.fr.vapor.com Starting nmap V. 2.3BETA14 by fyodor@insecure.org ( www.insecure.org/nmap/ ) Interesting ports on barney.umassmed.edu (146.189.121.87): Port State Protocol Service 111 open udp sunrpc 135 open udp loc-srv 137 open udp netbios-ns 138 open udp netbios-dgm 139 open udp netbios-ssn 1032 open udp iad3 $ nmap -sX ftp.fr.vapor.com Starting nmap V. 2.3BETA14 by fyodor@insecure.org ( www.insecure.org/nmap/ ) Interesting ports on barney.umassmed.edu (146.189.121.87): Port State Protocol Service 135 open tcp loc-srv 139 open tcp netbios-ssn $ nmap -sT ftp.blizzard.com Starting nmap V. 2.3BETA14 by fyodor@insecure.org ( www.insecure.org/nmap/ ) Interesting ports on ftp.blizzard.com (216.237.145.83): Port State Protocol Service 21 open tcp ftp 23 open tcp telnet 80 open tcp http 135 open tcp loc-srv 139 open tcp netbios-ssn 144 open tcp news 145 open tcp uaac 2112 open tcp kip $ nmap -sU ftp.blizzard.com Starting nmap V. 2.3BETA14 by fyodor@insecure.org ( www.insecure.org/nmap/ ) Interesting ports on ftp.blizzard.com (216.237.145.83): Port State Protocol Service 135 open udp loc-srv 137 open udp netbios-ns 138 open udp netbios-dgm 161 open udp snmp 407 open udp timbuktu $ nmap -sX ftp.blizzard.com Starting nmap V. 2.3BETA14 by fyodor@insecure.org ( www.insecure.org/nmap/ ) No ports open for host ftp.blizzard.com (216.237.145.83) Nmap run completed -- 1 IP address (1 host up) scanned in 6 seconds Hmm. SNMP open on this machine? Timbuktu? A telnet server? SunRPC? Some of these services kind of concern me -- it seems that these machines would be likely to be easily compromised, thus endangering the quality of the content that I could mirror from them. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message