From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 2/2] Suricata: Add port 3128 (Transparent Proxy) to group of HTTP ports.
Date: Wed, 01 Apr 2020 11:54:15 +0100 [thread overview]
Message-ID: <57236904-EC62-46CD-B94A-73226178F7DC@ipfire.org> (raw)
In-Reply-To: <93dc20f01caa8aa431e378e14bb9f2bc@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 943 bytes --]
> On 1 Apr 2020, at 11:24, Arne Fitzenreiter <arne_f(a)ipfire.org> wrote:
>
> I think it should be better to read the proxy config which port is used.
> Many installtions still use 800
Absolutely.
Why do we only add the transparent port here and not the default port?
-Michael
>
> Arne
>
>
> Am 2020-04-01 11:02, schrieb Stefan Schantl:
>> Fixes #12308.
>> Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
>> ---
>> config/suricata/suricata.yaml | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>> diff --git a/config/suricata/suricata.yaml b/config/suricata/suricata.yaml
>> index cb7ececb4..4a605c272 100644
>> --- a/config/suricata/suricata.yaml
>> +++ b/config/suricata/suricata.yaml
>> @@ -30,7 +30,7 @@ vars:
>> ENIP_SERVER: "$HOME_NET"
>> port-groups:
>> - HTTP_PORTS: "[80,81]"
>> + HTTP_PORTS: "[80,81,3128]"
>> SHELLCODE_PORTS: "!80"
>> ORACLE_PORTS: 1521
>> SSH_PORTS: "[22,222]"
prev parent reply other threads:[~2020-04-01 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 9:02 [PATCH 1/2] Suricata: Add port 81 (UpdateAccelerator) " Stefan Schantl
2020-04-01 9:02 ` [PATCH 2/2] Suricata: Add port 3128 (Transparent Proxy) " Stefan Schantl
2020-04-01 10:24 ` Arne Fitzenreiter
2020-04-01 10:54 ` 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=57236904-EC62-46CD-B94A-73226178F7DC@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