kill getsockopt unlink to
ReadWriteDirectories and commenting
SystemCallFilter=wait4 select futex read stat close openat fstat lseek mmap rt_sigaction getdents64 mprotect ioctl recvfrom munmap brk rt_sigprocmask fcntl getpid write access socket sendto dup2 clone execve getrandom geteuid getgid madvise getuid getegid readlink pipe rt_sigreturn connect pipe2 prlimit64 set_robust_list dup arch_prctl lstat set_tid_address sysinfo sigaltstack rt_sigsuspend shutdown timer_settime mkdir timer_create statfs getcwd setpgid setsockopt uname bind getpgrp getppid getpeername chdir poll getsockname fadvise64 clock_settime kill getsockopt unlink
Does that fix the issue?
March 23, 2021, 11:22am
That works better. However one issue remains.
process.wait(timeout_seconds) is broken. Hangs forever. To reproduce, try this:
timeout_seconds = 120
timeout_seconds = 2
And then restart sdwdate.
Meanwhile I will revert these changes to unbreak sdwdate in Whonix developers repository. Once this is fixed, I’ll look into it ASP.
I’m getting this error:
sdwdate - ERROR - General Timeout Error. Internet connection might be down.
However, it appears regardless of whether or not the sandboxing is enabled. It only happens after I change the variable you told me to. Are you sure this is a sandboxing error and not a code error?
There was before no such code error. Cannot totally rule out yet but only happened after enabling sandboxing. I’ll see that I can provide instructions for reproduction.
I couldn’t reproduce this anymore. Perhaps I made a mistake and tested the wrong version. sdwdate sandboxing is re-enabled in Whonix developers, testers, and stable-proposed-updates repository.
Thank you for another great contribution!
sdwdate is getting killed on Debian
buster on the
How to debug systemd hardening? All I get:
sdwdate.service: Main process exited, code=killed, status=31/SYS
Any way to see a more specific error message which systemd hardening was violated? Any other way to debug other than trial and error which the offensive option is?
Got an answer on reddit.
sudo journalctl _AUDIT_TYPE_NAME=SECCOMP -f
May 05 06:29:26 whonix1 audit: SECCOMP auid=4294967295 uid=108 gid=118 ses=4294967295 subj==/usr/bin/sdwdate (enforce) pid=9740 comm=“sdwdate” exe=“/usr/bin/python3.7” sig=31 arch=c0000015
syscall=140 compat=0 ip=0x7fff96cc7df4 code=0x0
Chromium OS Docs - Linux System Call Table for a table to translate
Maybe a better table:
Linux system calls table for several architectures
sdwdate with the systemd unit name to debug.)
sudoedit /lib/systemd/system/sdwdate.service && sudo systemctl daemon-reload && sudo systemctl restart sdwdate && sudo systemctl --no-page status sdwdate
This is great, I will already try the new SystemCallFilter, and if it does not work on arm64, I’ll follow your debug steps and open a PR.
Could you please try
sudo systemctl restart sdwdate after it succeeded once? Because first time its sets time using
date, subsequent ones using
sclockadj. Therefore it might work the first time but break later due to missing secomp whiltelisted syscalls.
I am not also wondering if removing/changing
SystemCallArchitectures setting would have been easier.
Also generally wondering if
SystemCallFilter is maintainable or will keep breaking when porting to the next version of Debian (
bullseye) or other platforms.
Oh, good catch, sorry for not checking that.
Opened another PR which now also works after restarting the service.
This is hard to expect.
Merged, and uploaded to Whonix developers repository.
@Patrick finally got time to check onion-grater
I did restart this a few time also. Anything else I should check?
Awesome, no, this one is straight forward to test.
@Patrick I realised that I missed one for sdwdate. The service started but the time never synched, now it does: