From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 4/4] firewall.menu: Drop entry for P2P-Block.
Date: Mon, 14 Feb 2022 21:12:15 +0000 [thread overview]
Message-ID: <856e79b6-2740-2f2b-b15a-9eedc2a080bb@ipfire.org> (raw)
In-Reply-To: <20220214190307.4086-4-stefan.schantl@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 909 bytes --]
Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>
> Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
> ---
> config/menu/50-firewall.menu | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/config/menu/50-firewall.menu b/config/menu/50-firewall.menu
> index 6ae9687dc..aa67d9007 100644
> --- a/config/menu/50-firewall.menu
> +++ b/config/menu/50-firewall.menu
> @@ -21,12 +21,6 @@
> 'title' => "$Lang::tr{'intrusion detection system'}",
> 'enabled' => 1,
> };
> - $subfirewall->{'50.p2p'} = {
> - 'caption' => $Lang::tr{'p2p block'},
> - 'uri' => '/cgi-bin/p2p-block.cgi',
> - 'title' => "P2P-Block",
> - 'enabled' => 1,
> - };
> $subfirewall->{'60.locationblock'} = {
> 'caption' => $Lang::tr{'locationblock'},
> 'uri' => '/cgi-bin/location-block.cgi',
next prev parent reply other threads:[~2022-02-14 21:12 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
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 [this message]
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=856e79b6-2740-2f2b-b15a-9eedc2a080bb@ipfire.org \
--to=peter.mueller@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