public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Tim FitzGeorge <ipfr@tfitzgeorge.me.uk>
To: development@lists.ipfire.org
Subject: IP Address Blacklists
Date: Sat, 15 Feb 2020 15:40:28 +0000	[thread overview]
Message-ID: <9fbe4688-0a26-b29e-58aa-f0853d4d1561@tfitzgeorge.me.uk> (raw)

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

Hi,

I've pushed the my changes to implement IP Address Blacklists to the
repository at git://git.ipfire.org/people/timf/ipfire-2.x.git on the
ipblacklist branch.

As a result of discussions with Michael, this has a number of changes
from my first patch series:

- Removed autoblacklist.
- Added WUI log pages.
- Removed status from settings WUI page.
- Simplified download.
- Modified sources file 'rate' to allow unit to be specified.
- Updated sources file 'disable' to allow list to be specified.
- Changed Dshield download URL to preferred address.
- Removed Abuse.ch blacklist (discontinued).
- Removed Talos Malicious blacklist (not appropriate).
- Added Feodo recommended blacklist.
- Added blocklist.de all blacklist.
- Updated ignored messages in logwatch.

There's also some additional code on the addresscheck branch which adds
a WUI page that can check why a URL or address is being blocked.  It's
not production ready, but may possibly be useful in testing.

Tim

             reply	other threads:[~2020-02-15 15:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-15 15:40 Tim FitzGeorge [this message]
2020-02-18 14:58 ` Michael Tremer
2020-02-18 16:49 ` ummeegge
2020-02-19 11:52   ` Michael Tremer
2020-02-19 17:13     ` ummeegge
2020-02-19 17:21       ` Michael Tremer
2020-02-19 18:43         ` ummeegge
2020-02-19 19:48           ` Thoughts regarding IP-based ad blockers (was: Re: IP Address Blacklists) Peter Müller
2020-02-19 22:47           ` IP Address Blacklists Tim FitzGeorge

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=9fbe4688-0a26-b29e-58aa-f0853d4d1561@tfitzgeorge.me.uk \
    --to=ipfr@tfitzgeorge.me.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