Our current best theory is that this was caused by the recent flip of coreutils-from to change cp back to uutils [1] and the bug report https://github.com/uutils/coreutils/issues/12191 (which only mentions macos but also is reproducible on Linux). The current rust-coreutils version in stonking seems to call chmod() on the symlinks it creates in the destination. chmod follows symlinks, so it rewrites the mode of whatever each link resolves to. Any setuid binary that something symlinks to therefore loses its setuid bit when a root filesystem tree is copied with cp -a.
The fix commits seem to be: - https://github.com/uutils/coreutils/commit/6954c467250dccfc04f5fc7e1a9b8e1dac32c517 - https://github.com/uutils/coreutils/commit/ab34a45c1981af9a65b712a5ecae2eb43b962979 [1]: https://launchpad.net/ubuntu/+source/coreutils-from/0.0.0~ubuntu29 ** Bug watch added: github.com/uutils/coreutils/issues #12191 https://github.com/uutils/coreutils/issues/12191 ** Also affects: rust-coreutils via https://github.com/uutils/coreutils/issues/12191 Importance: Unknown Status: Unknown ** Changed in: rust-coreutils (Ubuntu) Assignee: (unassigned) => Simon Johnsson (bamf0) ** Changed in: livecd-rootfs (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2165041 Title: Missing setuid flag in su and sudo To manage notifications about this bug go to: https://bugs.launchpad.net/rust-coreutils/+bug/2165041/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
