public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Rob Brewer <ipfire-devel@grantura.co.uk>
To: development@lists.ipfire.org
Subject: Re: ipblacklist V2
Date: Wed, 09 Feb 2022 13:23:41 +0000	[thread overview]
Message-ID: <su0f8t$inf$1@tuscan3.grantura.co.uk> (raw)
In-Reply-To: <1DC94D84-CE41-4A42-8195-27E14E542AAA@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1684 bytes --]

Hi Michael


Michael Tremer wrote:

> Hello Rob,
> 
> Thank you for your interest in working on this.
> 
> Yes, I always thought that there was great interest in moving this over
> the line. However, I could not find where we left off here.
> 
> There were a couple of outstanding issues that had to be resolved. I just
> couldn’t find my last emails. Are you aware of these?
> 

I'm pleased to say I have had an email from Tim and is supportive of my 
attempts to progress ipblacklist into IPFire. Tim however says "Between 
COVID, my taking on additional responsibilities and the code not being part 
of ipfire, it's currently got a very low priority for me."

Tim pointed me to his git pages where I was able to find most of the code 
that I thought was missing from patchwork and is all now installed on my 
firewall and is working extremely well.

You may be interested in one of the modification I have made to ipblacklist, 
is to add an additional local blacklist to the sources file to get a 
blocklist from a web server on my local network.  This is populated by a 
script which greps the mail server logs for SMTP Auth attacks and has been  
particularly useful in protecting the mail server from a recent botnet 
attack where the offending ip addresses have been recycled every one to 
three weeks. Currently the blocklist contains about 3000 ip addresses and 
has blocked nearly 2000 smtp auth attempts so far to-day.

I also use fail2ban and Banish to manage iptables blocks on the firewall.

The last communication I could find between yourself and Tim was in May 
2020. https://lists.ipfire.org/pipermail/development/2020-May/007822.html

Hope this is useful.

Rob



  parent reply	other threads:[~2022-02-09 13:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-04 18:17 Rob Brewer
2022-02-07 10:31 ` Michael Tremer
2022-02-07 12:58   ` Rob Brewer
2022-02-09 14:38     ` Adolf Belka
2022-02-09 21:43       ` Rob Brewer
2022-02-09 22:14         ` Adolf Belka
2022-02-10  9:45           ` Michael Tremer
2022-02-09 13:23   ` Rob Brewer [this message]
2022-02-09 14:29     ` Adolf Belka
2022-02-10  9:41     ` Michael Tremer
2022-02-10 15:12       ` Rob Brewer
2022-02-10 16:48         ` Michael Tremer
2022-02-12 21:29           ` Tim FitzGeorge
2022-02-13 12:44             ` Rob Brewer
2022-02-15 12:58               ` Michael Tremer
2022-02-15 12:54             ` Michael Tremer
     [not found] <ef8ac1dcde46b22207dde653d6717a95d2a737e7.camel@ipfire.org>
2022-03-01 13:13 ` Michael Tremer
2022-03-01 16:08 ` Rob Brewer
2022-03-05 18:52 ` Stefan Schantl
2022-03-05 21:46   ` Rob Brewer
2022-03-07 20:39     ` Michael Tremer
2022-03-07 22:54       ` Rob Brewer
2022-03-08 10:59         ` Rob Brewer
2022-03-08 15:45           ` Michael Tremer
2022-04-03  9:16           ` Stefan Schantl
2022-04-03 21:09             ` Rob Brewer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='su0f8t$inf$1@tuscan3.grantura.co.uk' \
    --to=ipfire-devel@grantura.co.uk \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox