From owner-freebsd-questions@freebsd.org Thu Oct 1 15:43:48 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C91FA0D464 for ; Thu, 1 Oct 2015 15:43:48 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 72A3F1221 for ; Thu, 1 Oct 2015 15:43:48 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 8F41320218 for ; Thu, 1 Oct 2015 11:43:41 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute6.internal (MEProxy); Thu, 01 Oct 2015 11:43:41 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=JRj9QMaAjQqisVG vFbAYd2w1X1U=; b=jAa9Jmm6Vit+werW8EXz9KjAsiq0qIUAfps76OTJP5LI511 UX8mYWURoLcZAReLsIDD3zemBAAI0K1LLVhTpQzTudgOsPcDPy2QHB/kJzudNHCN mzLF3apXZqHthCxZ7iD+STisORVKjfYc0HmOML5my24a9carMGxq9KTMAAW4= Received: by web3.nyi.internal (Postfix, from userid 99) id 60A9410A64E; Thu, 1 Oct 2015 11:43:41 -0400 (EDT) Message-Id: <1443714221.3983239.398738409.5D3608D5@webmail.messagingengine.com> X-Sasl-Enc: yYGY6IIpx8AmgjsWxvws5UEEAel06JX3zid5ELn0YDdH 1443714221 From: Mark Felder To: "Michael B. Eichorn" , Alexandre , FreeBSD Questions Mailing List FreeBSD Questions Mailing List MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-6d8d90a6 Subject: Re: SSHguard & IPFW Date: Thu, 01 Oct 2015 10:43:41 -0500 In-Reply-To: <1443531575.1236.13.camel@michaeleichorn.com> References: <1443531575.1236.13.camel@michaeleichorn.com> X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Oct 2015 15:43:48 -0000 On Tue, Sep 29, 2015, at 07:59, Michael B. Eichorn wrote: > > Is there any chance that you might have followed an old guide? In > sshguard < 1.5 a valid configuration option was to use syslog to kickoff > sshguard and not use sshguard enable, but this is now depreciated in > favor of the new 'Log Sucker' introduced in v1.5. > I noted a problem in the PR that was just opened: "Using sshguard via syslogd is convenient because it will auto-spawn a new process if sshguard were to die. However, if syslogd receives a HUP signal it sends a TERM to any piped children (by design). This kills sshguard, removing the entries from your firewall's sshguard table. You're now open to attacks by those on your blocklist until a new log entry makes syslogd spawn a new sshguard process. This is very bad." And syslogd can get HUPs hourly: # Rotate log files every hour, if necessary. 0 * * * * root newsyslog -- Mark Felder ports-secteam member feld@FreeBSD.org