bjorn3

Rustc has been able to find the sysroot based on the location of librustc_driver.so in addition to the location of the main executable for a while now.

This has the advantage that the actual source location of the failing command is shown, which is especially useful when multiple a test runs multiple commands. In addition the panic...

Fixes https://github.com/trifectatechfoundation/sudo-rs/issues/1080

Fix the compliance tests on Ubuntu

2

See the individual commits what needed to be changed.

Implement support for NOEXEC

9

This is using seccomp syscall filtering of the execve and execveat syscalls. Unlike the original sudo this does not depend on using LD_PRELOAD. Instead SECCOMP_RET_USER_NOTIF is used combined with a...

Compliance test failure with og sudo 1.9.16p1

1

This is the sudo version that will be in Debian Trixie. ``` ---- sudo::pam::env::default_and_override_pam_env_vars_are_parentheses_checked_but_set_vars_are_not stdout ---- Error: "program failed with exit code 1. stderr:\nsudo: pam_open_session: Critical error - immediate abort\nsudo:...

FreeBSD doesn't support seccomp, so this will have to load a dylib using LD_PRELOAD that overrides all the various exec* symbols that exist on FreeBSD.

Podman on FreeBSD currently puts each docker exec command in a jail with separate `/dev/pts`. This breaks the SIGWINCH tests. Once Podman fixes this, re-enable the corresponding tests.

This was done in https://github.com/sudo-project/sudo/commit/602a58e86a3562472499e339d40bed83e76109dc. Do we want to implement this too?

While sudo-rs correctly returns a non-zero exit code, sometimes on CI it seems like it fails to write the error message to stderr. I haven't been able to reproduce locally....