Marc Haber dixit:
>> whereas sudo reads the
>> tty from it, making it fail in chroots using qemu-user-static.
>
>How exactly does sudo fail? Is this worth reporting upstream?
Basically sudo does not ask for the password because it cannot
find its tty. I’ve mailed to the bugreport with you in X-De
Package: qemu
Version: 1:5.2+dfsg-6
Followup-For: Bug #940533
X-Debbugs-Cc: t...@mirbsd.de, Marc Haber
This bug is still pertinent. I’ve reproduced it locally right now as:
# mount an RPi Debian buster image (pristine Debian/arm64, not Raspian)
$ sudo losetup /dev/loop3 ~/tmp/rpi.img
$ sudo kpa
Hi Thorsten,
On Tue, Sep 17, 2019 at 12:33:26AM +0200, Thorsten Glaser wrote:
> linux-user/syscall.c:open_self_stat() fills the emulated
> /proc/self/stat with a lot of 0s,
So the contents of /proc/self/stat has the correct number of fields, but
all zeroes?
> whereas sudo reads the
> tty from it
On Tue, 17 Sep 2019, Thorsten Glaser wrote:
> linux-user/syscall.c:open_self_stat() fills the emulated
> /proc/self/stat with a lot of 0s, whereas sudo reads the
> tty from it, making it fail in chroots using qemu-user-static.
The weird thing is that /proc/$$/stat a.k.a. $(readlink /proc/self)/st
Package: qemu-user-static
Version: 1:4.1-1+b1
Severity: important
linux-user/syscall.c:open_self_stat() fills the emulated
/proc/self/stat with a lot of 0s, whereas sudo reads the
tty from it, making it fail in chroots using qemu-user-static.
Workaround: use sudo -S
-- System Information:
Debian
5 matches
Mail list logo
