From nobody Sat Apr 08 13:55:24 2023 X-Original-To: ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PtxZw72Cdz44TBL for ; Sat, 8 Apr 2023 13:55:36 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [66.165.241.226]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.nomadlogic.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PtxZv451Dz3pr0 for ; Sat, 8 Apr 2023 13:55:35 +0000 (UTC) (envelope-from pete@nomadlogic.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=nomadlogic.org header.s=04242021 header.b=2mlg7uBu; spf=pass (mx1.freebsd.org: domain of pete@nomadlogic.org designates 66.165.241.226 as permitted sender) smtp.mailfrom=pete@nomadlogic.org; dmarc=pass (policy=quarantine) header.from=nomadlogic.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomadlogic.org; s=04242021; t=1680962127; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=XZU4CbYETgUQT1c6X5sYHcbX0J0yvlnqTXnVYu2y+eI=; b=2mlg7uBuj5c9qehMF4BG4w7BeRUChnMTjVn1JFh0D95Uf8GiavA3s+4OTxc4B0KoWzqG5l HmmDdyb4vweQosGQ2pmgB0CZDaeP3/8BM7SsUlVBaI3er5jvlhk6249FRKwJvC7zIlTmxp Y5hoOn5vH/o9DEzHG79iLvY/i9ro6dg= Received: from [192.168.4.23] (c-66-176-247-235.hsd1.fl.comcast.net [66.176.247.235]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id b0c22fb7 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Sat, 8 Apr 2023 13:55:26 +0000 (UTC) Message-ID: Date: Sat, 8 Apr 2023 06:55:24 -0700 List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.9.1 Subject: Re: security/portsentry removal Content-Language: en-US To: ports@freebsd.org References: <0bfd94dd-5be3-6461-cb98-db1a1664e220@netfence.it> <3d779c56-236d-f18b-5ac0-71f6580bb498@bluerosetech.com> From: Pete Wright In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-3.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.978]; DMARC_POLICY_ALLOW(-0.50)[nomadlogic.org,quarantine]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[nomadlogic.org:s=04242021]; MIME_GOOD(-0.10)[text/plain]; DKIM_TRACE(0.00)[nomadlogic.org:+]; ASN(0.00)[asn:29802, ipnet:66.165.240.0/22, country:US]; MLMMJ_DEST(0.00)[ports@freebsd.org]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_DN_NONE(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[ports@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4PtxZv451Dz3pr0 X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N On 4/8/23 12:47 AM, Andrea Venturoli wrote: > On 4/8/23 04:56, Mel Pilgrim wrote: > >>> Can anyone suggest something equivalent in the port tree? >> >> Have a look at fail2ban.  It's design intent is monitoring running >> services, but really it's just a set of log file regex filters. >> Anything that logs network activity can feed it. > > Hello and thanks for answering. > In fact I'm already using fail2ban for "running" services. > > Portsenty is a bit different, in that it's conceived to listen on > ports used by non-running services. > I.e. > Got a SMTP server? Let fail2ban check its logs. > No? Let portsentry listen on port 25. > > I thought about writing regexes for fail2ban to check if ipfw denied > access to ports where portsentry used to listen. > So far it's the best idea I've come up with, but I hoped for something > simpler (i.e. more close to how portsentry worked). > would blacklistd(8) meet your requirements?  i use it to block ssh login spammers with decent success.  its part of the base system as well, but does require pf. -p