From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 2/4] configroot: Drop config file for p2protocols.
Date: Tue, 15 Feb 2022 12:33:16 +0000 [thread overview]
Message-ID: <25D4417A-DC0F-4034-AC7D-CD1CCA0E6E7B@ipfire.org> (raw)
In-Reply-To: <1497b9e9-618d-8db1-861c-2a20c620c643@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2279 bytes --]
Acked-by: Michael Tremer <michael.tremer(a)ipfire.org>
> On 14 Feb 2022, at 21:11, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>
>
>> The support for creating P2P based rules has been removed from the
>> firewall. So this file is not longer needed.
>>
>> Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
>> ---
>> config/firewall/p2protocols | 9 ---------
>> config/rootfiles/common/configroot | 1 -
>> lfs/configroot | 1 -
>> 3 files changed, 11 deletions(-)
>> delete mode 100644 config/firewall/p2protocols
>>
>> diff --git a/config/firewall/p2protocols b/config/firewall/p2protocols
>> deleted file mode 100644
>> index d8998095c..000000000
>> --- a/config/firewall/p2protocols
>> +++ /dev/null
>> @@ -1,9 +0,0 @@
>> -Applejuice;apple;on;
>> -Ares;ares;on;
>> -Bittorrent;bit;on;
>> -DirectConnect;dc;on;
>> -Edonkey;edk;on;
>> -Gnutella;gnu;on;
>> -KaZaA;kazaa;on;
>> -SoulSeek;soul;on;
>> -WinMX;winmx;on;
>> diff --git a/config/rootfiles/common/configroot b/config/rootfiles/common/configroot
>> index 904c718c3..fef5ffbcf 100644
>> --- a/config/rootfiles/common/configroot
>> +++ b/config/rootfiles/common/configroot
>> @@ -63,7 +63,6 @@ var/ipfire/firewall
>> #var/ipfire/firewall/input
>> #var/ipfire/firewall/locationblock
>> #var/ipfire/firewall/outgoing
>> -#var/ipfire/firewall/p2protocols
>> #var/ipfire/firewall/settings
>> var/ipfire/fwhosts
>> #var/ipfire/fwhosts/customgroups
>> diff --git a/lfs/configroot b/lfs/configroot
>> index 9f3188aab..b836767c1 100644
>> --- a/lfs/configroot
>> +++ b/lfs/configroot
>> @@ -105,7 +105,6 @@ $(TARGET) :
>> cp $(DIR_SRC)/config/firewall/convert-outgoingfw /usr/sbin/convert-outgoingfw
>> cp $(DIR_SRC)/config/firewall/convert-dmz /usr/sbin/convert-dmz
>> cp $(DIR_SRC)/config/firewall/convert-portfw /usr/sbin/convert-portfw
>> - cp $(DIR_SRC)/config/firewall/p2protocols $(CONFIG_ROOT)/firewall/p2protocols
>> cp $(DIR_SRC)/config/firewall/firewall-policy /usr/sbin/firewall-policy
>> cp $(DIR_SRC)/config/fwhosts/icmp-types $(CONFIG_ROOT)/fwhosts/icmp-types
>> cp $(DIR_SRC)/config/fwhosts/customservices $(CONFIG_ROOT)/fwhosts/customservices
next prev parent reply other threads:[~2022-02-15 12:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 19:03 [PATCH 1/4] firewall: Drop support for blocking P2P protocols Stefan Schantl
2022-02-14 19:03 ` [PATCH 2/4] configroot: Drop config file for p2protocols Stefan Schantl
2022-02-14 21:11 ` Peter Müller
2022-02-15 12:33 ` Michael Tremer [this message]
2022-02-14 19:03 ` [PATCH 3/4] p2p-block.cgi: Drop CGI Stefan Schantl
2022-02-14 21:12 ` Peter Müller
2022-02-15 12:33 ` Michael Tremer
2022-02-14 19:03 ` [PATCH 4/4] firewall.menu: Drop entry for P2P-Block Stefan Schantl
2022-02-14 21:12 ` Peter Müller
2022-02-15 12:32 ` Michael Tremer
2022-02-14 21:11 ` [PATCH 1/4] firewall: Drop support for blocking P2P protocols Peter Müller
2022-02-15 12:33 ` Michael Tremer
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=25D4417A-DC0F-4034-AC7D-CD1CCA0E6E7B@ipfire.org \
--to=michael.tremer@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