Re: qemu-user lost its entire viability
Thorsten Glaser <[email protected]> Sat, 23 Aug 2025 21:20:21 +0200 (CEST)
| Newsgroups | gmane.linux.debian.ports.superh,gmane.linux.debian.ports.68k |
|---|---|
| Message-ID | <[email protected]> |
On Sat, 23 Aug 2025, Michael Tokarev wrote: > This is impolite when you skip whole my explanation. Your explanation I snipped was unrelated to the problem. >> prompt> chroot --userspec=uname:gname /path/to/chroot /bin/sh >> chroot> do something >> chroot> sudo do something else > > This relied on an equivalent of your /bin/sh being suid-root. Then fix it. Make qemu-user check privilegues and drop them where not needed. Do not cop out breaking everything for users. > For this particular > workflow you have to find another way doing it, for example: > > prompt> chroot --userspec=uname:gname /path/to/chroot /bin/sh > chroot> do something > chroot> exit > prompt> chroot /path/to/chroot do something else This is impossible: when building packages in chroots, they have and *can* have an expectation that these things work. > I don't understand why you urge to return suid-root to your I don’t, I just fucking want the use case to continue working, and you map this as black-and-white and general “no, fuck off, I don’t even *try* to understand your use case and instead just tell you to not use it”. No thanks, //mirabilos -- Yes, I hate users and I want them to suffer. -- Marco d'Itri on gmane.linux.debian.devel.general