From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13671] openSSH server closes connection before authentication is finished
Date: Tue, 23 Mar 2021 22:32:27 +0000 [thread overview]
Message-ID: <bug-13671-163-QXrljJXbj4@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13671-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=13671
--- Comment #6 from Peter Seiderer <ps.report@gmx.net> ---
The following patch/hack fixed the problem for my testcase:
--- openssh-8.4p1/sandbox-seccomp-filter.c_orig 2021-03-23 23:15:02.131964000
+0100
+++ openssh-8.4p1/sandbox-seccomp-filter.c 2021-03-23 23:24:24.388408285
+0100
@@ -189,6 +189,11 @@
#ifdef __NR_clock_gettime
SC_ALLOW(__NR_clock_gettime),
#endif
+
+#ifndef __NR_clock_gettime64
+#define __NR_clock_gettime64 403
+#endif
+
#ifdef __NR_clock_gettime64
SC_ALLOW(__NR_clock_gettime64),
#endif
@@ -252,6 +257,11 @@
#ifdef __NR_clock_nanosleep
SC_ALLOW(__NR_clock_nanosleep),
#endif
+
+#ifndef __NR_clock_nanosleep_time64
+#define __NR_clock_nanosleep_time64 407
+#endif
+
#ifdef __NR_clock_nanosleep_time64
SC_ALLOW(__NR_clock_nanosleep_time64),
#endif
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-23 22:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 19:28 [Buildroot] [Bug 13671] New: openSSH server closes connection before authentication is finished bugzilla at busybox.net
2021-03-23 19:30 ` [Buildroot] [Bug 13671] " bugzilla at busybox.net
2021-03-23 20:01 ` bugzilla at busybox.net
2021-03-23 20:45 ` bugzilla at busybox.net
2021-03-23 21:16 ` bugzilla at busybox.net
2021-03-23 22:10 ` bugzilla at busybox.net
2021-03-23 22:32 ` bugzilla at busybox.net [this message]
2021-03-24 11:35 ` bugzilla at busybox.net
2021-03-25 21:09 ` bugzilla at busybox.net
2021-03-27 16:51 ` bugzilla at busybox.net
2021-03-28 17:41 ` bugzilla at busybox.net
2021-03-30 10:18 ` bugzilla at busybox.net
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-13671-163-QXrljJXbj4@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.