From: "Thompson, David" <dthompson2@worcester.edu>
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: Guile User <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: Guile security vulnerability w/ listening on localhost + port (with fix)
Date: Wed, 12 Oct 2016 12:11:30 -0400 [thread overview]
Message-ID: <CAJ=RwfYToxpvz06wK+ksHBvgSwZ-pEBadR7G4v+Y7ycgEfYr=A@mail.gmail.com> (raw)
In-Reply-To: <1476287379.10369.22.camel@gmail.com>
On Wed, Oct 12, 2016 at 11:49 AM, Nala Ginrut <nalaginrut@gmail.com> wrote:
> But maybe we should provide both just like what php-fpm does? And let users
> choose which one to use, localhost:port or unix socket.
This is what Guile already does.
- Dave
next prev parent reply other threads:[~2016-10-12 16:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 14:01 Guile security vulnerability w/ listening on localhost + port (with fix) Christopher Allan Webber
2016-10-12 15:49 ` Nala Ginrut
2016-10-12 16:11 ` Thompson, David [this message]
2016-10-14 21:55 ` Lizzie Dixon
2016-10-16 15:05 ` Christopher Allan Webber
2016-10-16 19:51 ` Arne Babenhauserheide
2016-10-17 1:39 ` Lizzie Dixon
2017-02-26 18:22 ` Andy Wingo
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='CAJ=RwfYToxpvz06wK+ksHBvgSwZ-pEBadR7G4v+Y7ycgEfYr=A@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=nalaginrut@gmail.com \
/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).