From owner-freebsd-hackers Tue May 6 10:58:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA24593 for hackers-outgoing; Tue, 6 May 1997 10:58:57 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA24587 for ; Tue, 6 May 1997 10:58:55 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA18862; Tue, 6 May 1997 10:54:28 -0700 From: Terry Lambert Message-Id: <199705061754.KAA18862@phaeton.artisoft.com> Subject: Re: divert still broken? To: danny@panda.hilink.com.au (Daniel O'Callaghan) Date: Tue, 6 May 1997 10:54:28 -0700 (MST) Cc: karpen@ocean.campus.luth.se, hackers@FreeBSD.ORG In-Reply-To: from "Daniel O'Callaghan" at May 6, 97 09:41:51 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > That doesn't mean that drop isn't a better keyword, and should be made an > > alias for deny. Although, if it wasn't for backwards compability (which we > > should keep, IMHO) then it would be better with: > > > > drop : be silent > > deny : send RST > > reject : send ICMP !H > > netreject : send ICMP !N > > > > But... that's not gonna happen, because we want backwards compability, > > so just forget I said it... :-) > > *laugh* I see what you are saying and No, I don't think we can rearrange > the keywords that much. deny/reject/netreject/resest will be it, I think. I like this. Is there any way you could institute a "version" keyword for command language versioning, at the top of the file? If not present, it falls back to the last grammar before the version keyword. You can "unsupport" a grammar by disallowing a version (it's unlikely that the grammar would change that significantly, though). Then you could normalize the command language at this point in time with the first known non-null version for the config file grammar. You want the new features? Well, buddy, you must put a varsion stamp in an fix the grammar entries. It's be pretty easy to cascade-convert an existing rules set with a sed script that starts by converting the old to the new keywords, and does it in "# of keywords" passes so that you never have two sets of meaning for "deny" (for example). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.