From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: 37309@debbugs.gnu.org
Subject: bug#37309: [PATCH] services: openssh: Restrict to IPv4.
Date: Tue, 10 Dec 2019 17:47:25 +0100 [thread overview]
Message-ID: <87tv68m8ki.fsf@gnu.org> (raw)
In-Reply-To: <20191204134135.GA7375@jasmine.lan> (Leo Famulari's message of "Wed, 4 Dec 2019 08:41:35 -0500")
Hi Leo,
Leo Famulari <leo@famulari.name> skribis:
> On Tue, Dec 03, 2019 at 10:53:11PM +0100, Julien Lepiller wrote:
>> Le 3 décembre 2019 21:12:51 GMT+01:00, Leo Famulari <leo@famulari.name> a écrit :
>> >+@item @code{address-family} (default: @code{'inet})
>> >+This is a symbol specifying which type of internet addresses should be
>> >+handled by @command{sshd}. The options are @code{inet} (IPv4),
>> >+@code{inet6} (IPv6), or @code{any}, which selects both @code{inet} and
>> >+@code{inet6}. The upstream default in @code{any}. However, we
>> default *is*
>
> Thanks!
>
> This patch did make sshd work for me again.
>
> However, as part of trying to debug this issue, I changed my system
> configuration so that it uses dhcp-client-service and
> wpa-supplicant-service instead of using Wicd. And now I can't reproduce
> the bug anymore.
>
> I guess that either 1) wpa_supplicant brings the network interfaces up
> faster or 2) the state of the network interfaces is more accurately
> captured with these services (in the sense of, is the network up?).
Did anyone manage to get an strace log as was discussed in
<https://issues.guix.gnu.org/issue/30993>?
That would allow us to know where this is hanging exactly (probably
bind(2) on an IPv6 address.)
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-12-10 16:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87k1da6fdb.fsf@roquette.mug.biscuolo.net>
[not found] ` <87y315t3hw.fsf@roquette.mug.biscuolo.net>
[not found] ` <87tvbhra2v.fsf@roquette.mug.biscuolo.net>
[not found] ` <87imrvhhpy.fsf@cbaines.net>
[not found] ` <874l3crjqr.fsf@roquette.mug.biscuolo.net>
[not found] ` <87k1c6p914.fsf@roquette.mug.biscuolo.net>
[not found] ` <20190817152031.GA3191@jurong>
[not found] ` <87pnkuyac0.fsf_-_@gnu.org>
[not found] ` <20190828181141.GA27765@jurong>
2019-09-05 13:18 ` bug#37309: ‘ssh-daemon’ service fails to start at boot Giovanni Biscuolo
2019-09-08 4:19 ` 宋文武
2019-11-26 18:34 ` Jelle Licht
2019-11-29 8:40 ` Giovanni Biscuolo
2019-11-29 9:51 ` Jelle Licht
2019-12-03 20:12 ` bug#37309: [PATCH] services: openssh: Restrict to IPv4 Leo Famulari
2019-12-03 21:53 ` Julien Lepiller
2019-12-04 13:41 ` Leo Famulari
2019-12-10 16:47 ` Ludovic Courtès [this message]
2020-11-27 23:00 ` bug#37309: ‘ssh-daemon’ service fails to start at boot Christopher Lemmer Webber
2020-11-28 1:08 ` Marius Bakke
2020-12-03 20:38 ` Leo Famulari
2020-12-03 21:56 ` Christopher Lemmer Webber
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tv68m8ki.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=37309@debbugs.gnu.org \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).