GNU bug report logs -
#18914
2.0.11 REPL server listens on 127.0.0.1 but not "localhost"
Previous Next
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Mon, 17 May 2021 22:43:41 +0200
with message-id <0917fc9d-2687-dd2d-6264-0cf8d999a4a2 <at> gmail.com>
and subject line 2.0.11 REPL server listens on 127.0.0.1 but not "localhost"
has caused the debbugs.gnu.org bug report #18914,
regarding 2.0.11 REPL server listens on 127.0.0.1 but not "localhost"
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
18914: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18914
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
After starting 'guile --listen', I can connect to it via 127.0.0.1 but
not "localhost": "Ncat: Connection refused." I don't know if
listening on "localhost" by default has any security implications?
Shell 1:
tub <at> taylan:~$ guile --listen
GNU Guile 2.0.11
Copyright (C) 1995-2014 Free Software Foundation, Inc.
Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
This program is free software, and you are welcome to redistribute it
under certain conditions; type `,show c' for details.
Enter `,help' for help.
scheme@(guile-user)>
Shell 2:
tub <at> taylan:~$ ncat localhost 37146
Ncat: Connection refused.
tub <at> taylan:~$ ncat 127.0.0.1 37146
GNU Guile 2.0.11
Copyright (C) 1995-2014 Free Software Foundation, Inc.
Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
This program is free software, and you are welcome to redistribute it
under certain conditions; type `,show c' for details.
Enter `,help' for help.
scheme@(guile-user)>
Taylan
[Message part 3 (message/rfc822, inline)]
I don't have access to the exact system anymore since it's been more than
6 years, but on a Debian with the exact same /etc/hosts I can't reproduce
the issue anymore. Since I was apparently the only one who could repro it
in the first place, I'm closing it now. :-)
Andy wrote:
> Could it be that "nc" is trying to connect to an IPv6 address?
Maybe that was the case on that system for some reason, despite the IPv4
address being on top in /etc/hosts and nslookup giving 127.0.0.1.
Maybe it was even a bug with the ncat I had installed, who knows.
--
Taylan
This bug report was last modified 4 years and 4 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.