public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Question regarding the forthcoming default firewall rule patch
Date: Thu, 26 Oct 2023 11:37:22 +0100	[thread overview]
Message-ID: <215D5812-4814-40DA-A66E-602304F2B7FB@ipfire.org> (raw)
In-Reply-To: <3a40cea1-f8a1-4ec4-9711-83c6d21980f2@ipfire.org>

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

Hello Peter,

I do not think that it should contain a link.

First of all, it won’t be clickable and as we don’t parse the comments and look for links. Secondly, we should not link to external websites that we don’t control like this. And last, but not least, the proposed PDF is really long and complicated and I don’t think that this is helpful to encourage people to keep that rule there.

So, simply “Block port 25 (TCP) for outgoing connections to the internet” should do it. More stuff should be referred to on the wiki.

-Michael

> On 26 Oct 2023, at 11:33, Peter Müller <peter.mueller(a)ipfire.org> wrote:
> 
> Hello Michael,
> hello *,
> 
> for the forthcoming patch, which introduces a firewall rule for rejecting TCP
> connections to destination port 25 on RED from all internal networks on new
> installations only, I'd like to clarify upfront what resource the rules' comment
> should link to, if any.
> 
> This could be a blog post by us, which would only go live shortly before the
> release of the Core Update this patch is merged into, so it will be a dead
> link at the time of patch submission.
> 
> Otherwise, linking to our wiki would work as well, or we can refer to the
> M3AAWG recommendation on this topic (https://www.m3aawg.org/Port25_IPNetworks)
> straight away.
> 
> Do you have any preferences?
> 
> Thanks, and best regards,
> Peter Müller (crawls back into the sewers)


      reply	other threads:[~2023-10-26 10:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26 10:33 Peter Müller
2023-10-26 10:37 ` 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=215D5812-4814-40DA-A66E-602304F2B7FB@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