From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: ipblacklist V2
Date: Mon, 07 Feb 2022 10:31:34 +0000
Message-ID: <1DC94D84-CE41-4A42-8195-27E14E542AAA@ipfire.org>
In-Reply-To: <stjqk4$v1j$1@tuscan3.grantura.co.uk>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============3575891210200900478=="
List-Id: <development.lists.ipfire.org>

--===============3575891210200900478==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

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 l=
ine. However, I could not find where we left off here.

There were a couple of outstanding issues that had to be resolved. I just cou=
ldn=E2=80=99t find my last emails. Are you aware of these?

-Michael

> On 4 Feb 2022, at 18:17, Rob Brewer <ipfire-devel(a)grantura.co.uk> wrote:
>=20
> Hi.
>=20
> I have been looking at Tim FitzGeorge's code for ipblacklist v2 on=20
> https://patchwork.ipfire.org/project/ipfire/list/?series=3D1215 to see if I=
=20
> can help progress its incorporation into IPFire.
> After I extracted the programs from Patchwork I have been able to build the=
m=20
> into my firewall where they are running very successfully.
> The code on the server seems to be in good shape and apart from a few small=
=20
> patches and additions of a few missing scripts I think it could be=20
> successfully introduced into the IPFire code base.
> I am more than happy to help in seeing this process carried out but need to=
=20
> know if this is acceptable to yourselves.
>=20
> Regards
> Rob Brewer


--===============3575891210200900478==--