From owner-freebsd-ports@FreeBSD.ORG Fri Jun 1 22:20:48 2007 Return-Path: X-Original-To: ports@FreeBSD.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6FADA16A400 for ; Fri, 1 Jun 2007 22:20:48 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from smtp2.utdallas.edu (smtp2.utdallas.edu [129.110.10.33]) by mx1.freebsd.org (Postfix) with ESMTP id 537CF13C458 for ; Fri, 1 Jun 2007 22:20:48 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from utd59514.utdallas.edu (utd59514.utdallas.edu [129.110.3.28]) by smtp2.utdallas.edu (Postfix) with ESMTP id E9EB35C13B for ; Fri, 1 Jun 2007 17:20:47 -0500 (CDT) Date: Fri, 01 Jun 2007 17:20:47 -0500 From: Paul Schmehl To: ports@FreeBSD.org Message-ID: <728AC552D218624D58E828C2@utd59514.utdallas.edu> In-Reply-To: References: X-Mailer: Mulberry/4.0.6 (Linux/x86) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=sha1; protocol="application/pkcs7-signature"; boundary="==========B655E2242D09CBDA4A1A==========" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: FreeBSD Port: ossec-hids-client-1.2 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jun 2007 22:20:48 -0000 --==========B655E2242D09CBDA4A1A========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On Thursday, May 31, 2007 14:21:58 -0700 Andrew Storms=20 wrote: > Reporting some problems. > > Based on how things got installed the start script at > /usr/local/etc/rc.d/ossec-hids Points to the wrong 'command' and > 'required_files'. > > > command=3D"/usr/local/bin/ossec-control" > Whereas 'ossec-control' got installed at '/usr/local/ossec-hids/bin' > > And > required_files=3D"/usr/local/etc/ossec.conf" > The ossec.conf file was actually installed at = '/usr/local/ossec-hids/etc'. > > > I also noticed that even though one chooses to install > ossec-hids-client-1.2 and not the server, what's actually installed is > the server. Though the ossec.conf file appears to be for a client, if > one runs the 'manage-agents' binary you receive the options as if this > was a server installation. I honestly haven't dug into why this one is > happening. My guess would be something got missed in the Make options. > > Nonetheless, I'm excited to see a port for OSSEC. > I can't believe this port got committed. There are three conf files in the = source; server, client and local. Only one is referenced in the master=20 Makefile and even *it* doesn't get installed because the syntax is=20 incorrect. The startup script is useless as well. That's just what I found in a=20 cursory examination. This port needs a ton of work before it's ready to go into the tree. I'll=20 see what I can do about submitting PRs over the weekend. --=20 Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ --==========B655E2242D09CBDA4A1A==========--