unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Greg Troxel <gdt@lexort.com>
To: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: [PATCH] web: default to INADDR_ANY instead of INADDR_LOOPBACK
Date: Fri, 22 Jul 2022 07:45:32 -0400	[thread overview]
Message-ID: <rmiczdxs74z.fsf@s1.lexort.com> (raw)
In-Reply-To: CA+XASoU51=kH9=a0UU4tyeewq-Gd1PHhCjgV+gPm3+o8d-8=RQ@mail.gmail.com

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


Aleix Conchillo Flaqué <aconchillo@gmail.com> writes:

>> Using INADDR_ANY instead of INADDR_LOOPBACK makes it convenient when
>> starting the web server inside containers without the need to having to
>> specify INADDR_ANY all the time. This is the default in most libraries
>> and languages.

I may be an outlier, but I don't think we should optimize for
containers.  I think that by default, most things that can reasonably
just listen on localhost should and those that want wider scope can
configure them (which should be easy and apparently is).

It seems this was an earlier conscious choice, from reading the patched docs.

>> This doesn't break backwards compatibility since INADDR_LOOPBACK is also
>> included in INADDR_ANY.

It does break compat because the previous way had a security property
that this one doesn't.  This is fundamentally a disagreement about what
"works" means.  Some people think works primarily means "when I click X
I see Y" and others thinks works primarily means "security properties
(that nothing bad happens" are upheld".

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]

  parent reply	other threads:[~2022-07-22 11:45 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é
2022-07-22 11:45   ` Greg Troxel [this message]
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=rmiczdxs74z.fsf@s1.lexort.com \
    --to=gdt@lexort.com \
    --cc=aconchillo@gmail.com \
    --cc=guile-devel@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).