From owner-freebsd-ports@FreeBSD.ORG Sat Sep 13 16:20:01 2014 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4BCA2AF2 for ; Sat, 13 Sep 2014 16:20:01 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DB437A92 for ; Sat, 13 Sep 2014 16:20:00 +0000 (UTC) Received: from [192.168.0.100] ([188.21.181.54]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0MSMP5-1Xw9Ie1eWJ-00TS65; Sat, 13 Sep 2014 18:19:47 +0200 Message-ID: <54146E99.4060400@gmx.at> Date: Sat, 13 Sep 2014 18:19:37 +0200 From: Christoph Theis User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Stavros Patiniotis Subject: Re: FreeBSD Port: py27-fail2ban-0.9.0_2 References: <0c4801cfcee6$eaaa1a10$bffe4e30$@staff.esc.net.au> In-Reply-To: <0c4801cfcee6$eaaa1a10$bffe4e30$@staff.esc.net.au> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K0:NsgEkKmc64Yu6V1jhDlDrKTV2PugvsqKWNos5gptIKv4Nb+Eh2q R2cwHiM5iGQyMsSEcAtbO5GiJZt0tmwkXa0axVk8BmIBuaIU7KUXj08P4tKHl+OU0YYhetR Nl8C7vJrWpe6hJLpSTBklvLvzil3snooIKFURxCztWf1MqhWyhTWp7bhDo2HKYeuiFIstSg ALL2YCrS0vDmST+tcBJxw== X-UI-Out-Filterresults: notjunk:1; Cc: ports@FreeBSD.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Sep 2014 16:20:01 -0000 Hello! Am 13.09.2014 um 02:08 schrieb Stavros Patiniotis: > Hello, > > I’ve been trying to work out why logging via syslog does not function > and found that fail2ban has a hard coded socket for the syslog daemon > which is not BSD compatible. Here is a patch to resolve, otherwise pass > it upstream to have the project make it a configuration directive. Thank you for finding that. I've never used fail2ban with log files only. I will pass it upstream but I don't know when 0.9.1 will come out. So in the meantime I will make a patch for FreeBSD, there are some more small issues waiting to be fixed. Best regards Christoph