On Sat, Jan 04, 2020 at 09:35:27AM +0100, Giovanni Mascellani wrote: > I suspect the problem might be related to the fact that /usr/bin/schroot > is not set-uid anymore, while it was before. Executing > ...
I ran into this as well and verified on another system running sid that the binary update to 1.6.10-7 is when the setuid bit is removed - it's simply not set in the binary package, while it is in . I'm curious as to how this happened. I not seeing anything obvious in the source package changes [1], and when I rebuild 1.6.10-6 or 1.6.10-7 from source locally in a sid chroot, neither one of them results in a setuid binary. In the build logs for those builds, the install-arch target is no longer being called. However, building 1.6.10-7 in a buster chroot does result in a setuid binary, so it seems that a recent change in the packaging toolchain could be the root cause (although I haven't found anything definitive yet). Cheers, tony [1] https://salsa.debian.org/debian/schroot/compare/2ba1e043...e3358529
