public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: Adolf Belka <adolf.belka@ipfire.org>
Cc: development@lists.ipfire.org
Subject: Re: [PATCH] ipblocklist-functions.pl: Specify an IPFire user agent for the downloads
Date: Wed, 12 Mar 2025 16:34:36 +0000	[thread overview]
Message-ID: <23102622-D7F5-451E-96F3-F34DAEF3E24A@ipfire.org> (raw)
In-Reply-To: <20250312144610.3254927-1-adolf.belka@ipfire.org>

Very interesting. I wasn’t even aware that we had this function.

> On 12 Mar 2025, at 14:46, Adolf Belka <adolf.belka@ipfire.org> wrote:
> 
> - As discussed at the IPFire conf call in March 2025, this patch provides an IPFire
>   specific User Agent string for the IP Block Lists downloads using LWP::UserAgent.
> - It turned out that there was already a function in general-functions.pl that creates
>   an IPFire Useer Agent string. This was used for this IP Blocklist download.
> - Currently it gave me the string IPFire/2.29/192.
> - This was tested out with the Threatview.io IP blocklist download and it worked fine.
> - If this patch is approved and merged then I will let contact Threatview.io to let them
>   know what our User Agent string is.
> 
> Tested-by: Adolf Belka <adolf.belka@ipfire.org>
> Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
> ---
> config/cfgroot/ipblocklist-functions.pl | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/config/cfgroot/ipblocklist-functions.pl b/config/cfgroot/ipblocklist-functions.pl
> index bd026a01d..665dadb4c 100644
> --- a/config/cfgroot/ipblocklist-functions.pl
> +++ b/config/cfgroot/ipblocklist-functions.pl
> @@ -2,7 +2,7 @@
> ###############################################################################
> #                                                                             #
> # IPFire.org - A linux based firewall                                         #
> -# Copyright (C) 2007-2022  IPFire Team  <info@ipfire.org>                     #
> +# Copyright (C) 2007-2025  IPFire Team  <info@ipfire.org>                     #
> #                                                                             #
> # This program is free software: you can redistribute it and/or modify        #
> # it under the terms of the GNU General Public License as published by        #
> @@ -118,13 +118,15 @@ sub download_and_create_blocklist($) {
> use LWP::UserAgent;
> 
> # Create a user agent for downloading the blacklist
> + # Define the User Agent string
> # Limit the download size for safety
> + my $user_agent = &General::MakeUserAgent();
> my $ua = LWP::UserAgent->new (
> ssl_opts => {
> SSL_ca_file     => '/etc/ssl/cert.pem',
> verify_hostname => 1,
> },
> -
> + agent => $user_agent,
> max_size => $max_dl_bytes,
> );
> 
> -- 
> 2.48.1
> 
> 



      reply	other threads:[~2025-03-12 16:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-12 14:46 Adolf Belka
2025-03-12 16:34 ` Michael Tremer [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=23102622-D7F5-451E-96F3-F34DAEF3E24A@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=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