proot
proot copied to clipboard
proot-me
chroot, mount --bind, and binfmt_misc without privilege/setup for Linux
How to reproduce: ``` shell-1$ /usr/bin/sleep 999 ``` then in another prooted shell: ``` shell-2$ gdb -p [...] (gdb) x /i $pc => 0x7f29946dced0 : cmp $0xfffffffffffff001,%rax (gdb) quit A...
That way, both initial and reproduced executions use the same code (in the standard C library). Today, this can be achieved by setting LD_HWCAP_MASK to 0 before starting CARE.
Step to reproduce: ``` echo >1 # not touch, size must be >0 chmod -w 1 # must be read only proot -0 tar -cf 1.tar 1 /bin/tar: 1: file...
- Host: Slackware-14.1/Linux-3.10.17/x86_64 - Guest: Ubuntu-13.04/x86 - Command: proot -R ubuntu-13.04-x86 epsxe - Output: proot warning: process 4183 is doing suspicious brk() Running ePSXe emulator version 1.9.4. [...]
It would be really hanldy to be able to extract, re-execute and remove the result of the extraction in only one command. Something like: ``` ./foo.bin ./foo/re-execute.sh rm -rf foo/...
Details: https://linuxfr.org/nodes/101156/comments/1518591
Details: http://linuxfr.org/news/care-et-la-reproductibilite-des-executions#comment-1517970
Running "uname -a" under care gave different answers depending on the. First execution on hostA: $ care -o care-uname.tar uname -a Linux hostA 3.11-2-amd64 #1 SMP Debian 3.11.8-1 (2013-11-13) x86_64...
> Yes it is released (version 5.0.0), it crashes Free Pascal that > worked before - apt-get install fp-compiler-2.6.0 crashes with > segfault. I wonder if Gnuroot also suffers from...
How to reproduce: ``` proot-v3.2.2 -w / -r stage3-x32-20140508 true ``` Current result: ``` proot info: pid 21592: terminated with signal 11 ``` Note: this used to work (c.f. commit...