public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Add Ellio Community feed to ipblocklist/sources
Date: Wed, 13 Sep 2023 14:03:17 +0200	[thread overview]
Message-ID: <90d8e367-e457-466e-89c3-2b4485585816@ipfire.org> (raw)
In-Reply-To: <1EC28A5A-B15E-4687-A36E-4145177C6358@ellio.tech>

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

Hallo Ayush,

Looking through the wording at the top of the Ellio community feed it says the following:-

"It is intended solely for the individual's own internal use in efforts to improve their cybersecurity posture or for other non-commercial purposes."

It seems to me that wording above could mean that a business that has installed IPFire on a machine for their firewall protection might not be allowed to use your community IP Block Lists.

Your website talks about the use of the Community Block List as only for HomeLabers and Tech Enthusiasts. To get included in the IPFire system the block list would need to be able to be used by any of our users including businesses.

Are you able to confirm that there would be no restriction on the use of the Block List for any IPFire user?


Regards,

Adolf Belka


On 13/09/2023 12:50, Ayush Tomar wrote:
>  From 13c58a87843a73df34d370edc7c505eb6b6c60f3 Mon Sep 17 00:00:00 2001
> From: Ayush Tomar <ayush.tomar(a)ellio.tech>
> Date: Wed, 13 Sep 2023 11:32:43 +0200
> Subject: [PATCH] Add Ellio Community feed to ipblocklist/sources
>
> ---
>   config/ipblocklist/sources | 6 ++++++
>   1 file changed, 6 insertions(+)
>
> diff --git a/config/ipblocklist/sources b/config/ipblocklist/sources
> index be0cf0229..26699ff56 100644
> --- a/config/ipblocklist/sources
> +++ b/config/ipblocklist/sources
> @@ -67,6 +67,12 @@ our %sources = ( 'EMERGING_FWRULE' => { 'name'     => 'Emerging Threats Blocklis
>                                       'parser'   => 'dshield',
>                                       'rate'     => '1h',
>                                       'category' => 'attacker' },
> +            'ELLIO_TECH'         => {'name'     => 'ELLIO: IP Feed (Community version)',
> +                                    'url'      => 'https://cdn.ellio.tech/community-feed',
> +                                    'info'     => 'https://ellio.tech',
> +                                    'parser'   => 'ip-or-net-list',
> +                                    'rate'     => '24h',
> +                                    'category' => 'attacker' },
>                'FEODO_RECOMMENDED'=> {'name'     => 'Feodo Trojan IP Blocklist (Recommended)',
>                                       'url'      => 'https://feodotracker.abuse.ch/downloads/ipblocklist_recommended.txt',
>                                       'info'     => 'https://feodotracker.abuse.ch/blocklist',

      reply	other threads:[~2023-09-13 12:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13 10:50 Ayush Tomar
2023-09-13 12:03 ` Adolf Belka [this message]

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=90d8e367-e457-466e-89c3-2b4485585816@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --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