Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT cygwin DOT com Message-ID: <3C62CD15.7040703@ece.gatech.edu> Date: Thu, 07 Feb 2002 13:53:09 -0500 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: prentis AT aol DOT net CC: cygwin-apps AT cygwin DOT com Subject: Re: TCP Wrappers References: <200202071804 DOT NAA19867 AT imap DOT web DOT aol DOT com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Prentis Brooks wrote: > Alright, > finally read over the setup.html file and built up the src and binary > packages. Writing up the setup.hint file now. I have the following: > > # TCP Wrappers > @ tcp_wrappers_7.6 This line is not necessary -- it is created in setup.ini by the upset script; it doesn't need to appear in setup.hint > sdesc: "TCP Wrappers" You don't need to put the name into the descriptions anymore; setup.exe will automatically add the name. I would suggest sdesc: "Tool to provide host based access restrictions in tcp services" ldesc: "With this package you can monitor and filter incoming requests for the SYSTAT, FINGER, FTP, TELNET, RLOGIN, RSH, EXEC, TFTP, TALK, and other network services. The package provides tiny daemon wrapper programs that can be installed without any changes to existing software or to existing configuration files. The wrappers report the name of the client host and of the requested service; the wrappers do not exchange information with the client or server applications, and impose no overhead on the actual conversation between the client and server applications." > ldesc: "TCP Wrappers: Tool to provide host based access restrictions to tcp > base > d services" > skip: > curr: 7.6 > prev: > test: You don't need to specify these at all. The upset script will figure it out and put "the right thing" into setup.ini. You only need to specify these manually within setup.hint if the upset parser gets it wrong. > category: > requires: category: Net requires: cygwin > > Does what I have look right, and what category should I put this into? I > don't think this requires much beyond cygwin. Going to look at the setup.ini > to see if there are other requirements that make sense. > > Feedback appreciated. > > --Chuck