From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: [PATCH] web: default to INADDR_ANY instead of INADDR_LOOPBACK
Date: Fri, 22 Jul 2022 10:14:54 -0700 [thread overview]
Message-ID: <CA+XASoX7A8da0AoU8i6AURr-X02a46979va76_A6owEstuHa7Q@mail.gmail.com> (raw)
In-Reply-To: <8d7255ee-07b2-bd66-2e33-75c8d112756e@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 1696 bytes --]
Thank you Maxime,
On Fri, Jul 22, 2022 at 2:44 AM Maxime Devos <maximedevos@telenet.be> wrote:
> On 22-07-2022 02:44, Aleix Conchillo Flaqué wrote:
>
> ping. easy one but might be more controversial.
>
> On Wed, Feb 2, 2022 at 4:26 PM Aleix Conchillo Flaqué <
> aconchillo@gmail.com> wrote:
>
>> Using INADDR_ANY instead of INADDR_LOOPBACK makes it convenient when
>> starting the web server inside containers
>
> I don't see what containers have to do with anything? If you want it to
> access the Internet, just don't do a network container (don't create a new
> network namespace). Or to reduce access, do create a new network namespace
> but set up port forwarding (which I would expect to work with loopback).
>
Now that I read it again, I have no clue what containers have to do with
this either, especially because I never run Guile in a container... So,
forget about the container reference.
> without the need to having to
>> specify INADDR_ANY all the time.
>>
> I don't recommend this as a default, as it opens up potential security
> problems (some programs open a web server for local communication on the
> computer). INADDR_LOOPBACK is a safe default, anyone needing something else
> and knowing their use is safe can easily override to INADDR_ANY.
>
> This is the default in most libraries and languages.
>
> Is ad populum. Plenty of bad choices have been made in the past, see e.g.
> all the CVEs, so I don't think this is a good argument. (It is an argument
> if you are switching to INADDR_ANY for _consistency_, but the patch appears
> to be for other purposes.)
>
>
Makes sense. Thank you for the reply!
Best,
Aleix
[-- Attachment #2: Type: text/html, Size: 3898 bytes --]
next prev parent reply other threads:[~2022-07-22 17:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 0:26 [PATCH] web: default to INADDR_ANY instead of INADDR_LOOPBACK Aleix Conchillo Flaqué
2022-02-03 7:25 ` Dr. Arne Babenhauserheide
2022-07-22 0:44 ` Aleix Conchillo Flaqué
2022-07-22 9:44 ` Maxime Devos
2022-07-22 17:14 ` Aleix Conchillo Flaqué [this message]
2022-07-22 11:45 ` Greg Troxel
2022-07-22 17:16 ` Aleix Conchillo Flaqué
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+XASoX7A8da0AoU8i6AURr-X02a46979va76_A6owEstuHa7Q@mail.gmail.com \
--to=aconchillo@gmail.com \
--cc=guile-devel@gnu.org \
--cc=maximedevos@telenet.be \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).