View Single Post
Old 02-15-2026, 04:02 PM   #117
SilverGreen93
Member
SilverGreen93 began at the beginning.
 
Posts: 24
Karma: 10
Join Date: Nov 2019
Device: Pocketbook InkPad Color 3
Code:
mm_reap: child terminated by signal 31
debug1: do_cleanup
debug1: Killing privsep child 9062
Doesn't this mean that the ssh process is to blame? I don't see any indicator that my key was not accepted.

Maybe it is not compiled correctly to match the kernel version and it can't do syscalls?

From stackoverflow:
Quote:
Signal 31 is SIGSYS, which is most commonly raised by seccomp, which sshd normally uses for privilege separation.

Due to this, the version of sshd needs to match the kernel version at least approximately, otherwise sshd won't be able to whitelist all the needed syscalls, for example, clock_gettime64.

When building sshd from source, check that /usr/include/linux/version.h matches your actual kernel version (normally the case when you have linux-headers installed, but may not be the case when cross-compiling).
I have software version 6.10.2854

Last edited by SilverGreen93; 02-15-2026 at 04:10 PM.
SilverGreen93 is offline   Reply With Quote