v4.0.3 - Many bugfixes

What's Changed

• chore: create_with_privileges, remove_with_privileges and create_dir_all_with_privileges are no longer used
• chore: enable clippy::undocumented_unsafe_blocks, test modules are allowed like in sudo-rs
• chore: SAFETY comments of cutils.rs, securemem.rs and rpassword.rs are taken from sudo-rs
• fix: the monitor process exits with _exit to not run the atexit handlers of the parent
• fix: the hierarchy plugin notifies events while its callback runs, the API is now a RefCell borrowed immutably during notifications
• fix: raise CAP_FOWNER to change file flags whenever the file is not owned by the user
• fix: mark file descriptors above stderr close-on-exec with close_range, fallback on /proc/self/fd
• fix: an error while handling file descriptors now aborts the execution instead of being ignored
• fix: setting capabilities returns an error instead of panicking in the child
• fix: the tty is the controlling terminal, not the device behind stdout
• fix: tty cookies are bound to the session leader and ppid cookies to the parent, both with their start time, so a recycled pid does not match
• fix: without a controlling terminal, tty cookies fall back to the parent process instead of being valid for every process of the user
• fix: cookie times use CLOCK_BOOTTIME, cookies from the future are rejected
• fix: the timestamp directory and cookie files are created owned by root, opened without following symbolic links and checked before use
• fix: insecure cookie files left by previous versions are replaced
• fix: replace the racy lockfile by a flock on the cookie file
• fix: failing to save a cookie no longer aborts the session
• fix: remove forgotten debug logging of session I/O to /tmp/dosr-session.log
• chore: remove RAR_MAX_LOCKFILE_RETRIES and RAR_LOCKFILE_RETRY_INTERVAL
• chore: SimpleFileLogger creates its file with mode 0600 and never follows symlinks

Full Changelog: v4.0.2...v4.0.3