Package: proot Version: 5.1.0-1.1 Severity: normal Tags: upstream Hello,
It seems proot 5.1.0-1.1, as found in Debian Sid as I am reporting this, is unusable. How to reproduce? $ # Work around https://github.com/proot-me/PRoot/issues/106 $ export PROOT_NO_SECCOMP=1 $ proot ls proot error: can't write the loader: Bad address proot error: execve("/bin/ls"): No such file or directory proot info: possible causes: * the program is a script but its interpreter (eg. /bin/sh) was not found; * the program is an ELF but its interpreter (eg. ld-linux.so) was not found; * the program is a foreign binary but qemu was not specified; * qemu does not work correctly (if specified); * the loader was not found or doesn't work. fatal error: see `proot --help`. Expected outcome: this command should have listed the current directory. A short investigation reveals that proot fails to determine the size of the binary loader (it gets a garbage value), leading to that "can't write the loader" error when the said garbage value is fed to write(). Fortunately, a fix is available upstream: https://github.com/proot- me/PRoot/pull/108 And I can confirm that building the "hotfixLoader" branch makes proot usable again. Cheers, Xavier. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages proot depends on: ii libc6 2.24-7 ii libtalloc2 2.1.8-1 proot recommends no packages. proot suggests no packages. -- no debconf information
