Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 15 Sep 2002 00:56:37 -0400
From:      Alan E <alane@geeksrus.net>
To:        "David O'Brien" <obrien@freebsd.org>
Cc:        FreeBSD Ports List <ports@freebsd.org>
Subject:   Re: bash2 ports
Message-ID:  <20020915045637.GA89023@wwweasel.geeksrus.net>
In-Reply-To: <20020915000122.GB96824@dragon.nuxi.com>
References:  <20020914202751.GA78262@wwweasel.geeksrus.net> <20020915000122.GB96824@dragon.nuxi.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Sep 14, 2002 at 05:01:22PM -0700, David O'Brien wrote:
>On Sat, Sep 14, 2002 at 04:27:52PM -0400, Alan E wrote:
>> I am currently hosting the bash2 port files on
>> 	http://people.freebsd.org/~alane/bash2/
>> but do not wish to do so indefinitely.
>> 
>> The default ipfw firewall and inetd configuration will not allow
>> fetching the files for this port, due to the policies of the master
>> hosting site.
>
>What are the policies of the master hosting site?  Has anyone emailed
>Chet (bash2 author) to try to determine why they have trouble fetching
>the bash2 patches?

One of the posters has emailed chet, and got no reponse. He's also been
copied of a large amount of the correspondence.

>I run "options IPFIREWALL" in my kernel with a modified "simple"
>rc.firewall type (kept existing rules and added more).  I have *ZERO*
>problems fetching the bash2 patch files from ftp.cwru.edu.

The problem is that the default is deny, not send a reset. The problem
is that their site tries to do an indentd lookup and when the firewall
drops the packet on the floor, you don't get in.

>> I find this to be an intolerable situation, and either we need to modify
>> our shipped inetd.conf and rc.firewall to accomodate this port (hahaha)
>> or we need to find a permanent home on a freebsd server for its files.
>
>FreeBSD doesn't enable ipfw firewall by default.  So I don't know what
>you are talking about.

But I don't think that running a stock ipfw firewall can be considered a 
very non-standard situation, as unless you're already behind one,
running a firewall is the smart thing to do.

All I wanted out of you was for you to host the files for bash2 in your
~/public_distfiles (at least 2 port versions worth), and add the URL as
a MASTER_SITE and PATCH_SITE.

-- 
Alan Eldridge
Unix/C(++) IT Pro, 20 yrs, seeking new employment.
(http://wwweasel.geeksrus.net/~alane/resume.txt)
KDE, KDE-FreeBSD Teams (http://www.kde.org, http://freebsd.kde.org/)

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020915045637.GA89023>