https://bugzilla.mindrot.org/show_bug.cgi?id=3430
--- Comment #5 from Darren Tucker <[email protected]> --- (In reply to Lacky from comment #4) > As you said sshd doesn’t add > clock_gettime64 as an allowed syscall to seccomp because it cannot > find it in kernel headers. This is the root of the problem. Why isn't __NR_clock_gettime64 defined? I have a Debian 11 32bit ARM system here with glibc 2.31 and it has it: $ uname -a Linux tock 5.16.10-bone14 #1bullseye PREEMPT Tue Feb 22 00:07:39 UTC 2022 armv7l GNU/Linux $ sudo dpkg -l | grep libc-bin ii libc-bin 2.31-13+deb11u3 armhf GNU C Library: Binaries $ grep -r __NR_clock_gettime64 /usr/include/* [...] /usr/include/asm-generic/unistd.h:#define __NR_clock_gettime64 403 /usr/include/asm-generic/unistd.h:__SYSCALL(__NR_clock_gettime64, sys_clock_gettime) I confirmed it's set in sshd (to 403) by adding a debug call. What distro are you using? -- You are receiving this mail because: You are watching someone on the CC list of the bug. You are watching the assignee of the bug. _______________________________________________ openssh-bugs mailing list [email protected] https://lists.mindrot.org/mailman/listinfo/openssh-bugs
