chroot, mount --bind, and binfmt_misc without privilege/setup for Linux, https://proot-me.github.io
though I guess its possible you are just merging it and then building on it haha
I did see something about seccomp mode being supported on that given proot
so in that case is ptrace not used?
hm, not sure what happened there then though I didnt read the output very carefully
specifically for stracing though you cant ptrace a ptrace so that shouldnt work
hmmmmm
the other possibility is that strace is using seccomp for tracing, unless i completely misunderstood everything and this isnt even a thing
--seccomp-bpf
Try to enable use of seccomp-bpf (see seccomp(2)) to have ptrace(2)-stops only when system calls that are being traced occur in the traced processes. This option has no effect unless -f/--follow-forks is also
specified. --seccomp-bpf is also not applicable to processes attached using -p/--attach option. An attempt to enable system calls filtering using seccomp-bpf may fail for various reasons, e.g. there are too many
system calls to filter, the seccomp API is not available, or strace itself is being traced. In cases when seccomp-bpf filter setup failed, strace proceeds as usual and stops traced processes on every system call.
I don't 100% understand what this is sayng
it only fails to ptrace processes that are already being ptraced but works otherwise?
well that wouldnt help much for proot since its ptracing everything (?)
1 reply
(wouldnt proot have to be ptracing all children to work?)
But if a program doesn't allow ptrace then it won't work
So you can use gdb or strace on PRoot itself... but depends on what runs inside the PRoot if you can ptrace it
well half my problem was I kept messing up a file name, so I did end up solving it with the fake mounts, but I was more wondering if (I really should just check with -v) internal mount --bind could /is be caught and emulated (if that makes sense)
1 reply
oxr463: another suggestion: allow specifying a file to output -v output to
proot info: vpid 47: translate("/" + "/nix/store/ga9q4ikprn36wm32gqm4k521iv9kic5p-libsodium-1.0.18/lib/libsodium.so.23")
proot info: vpid 47: -> "/Lustre01/home/qosnebc/pls/store/ga9q4ikprn36wm32gqm4k521iv9kic5p-libsodium-1.0.18/lib/libsodium.so.23.3.0"
proot info: vpid 47: sysenter start: read(0x3, 0x7fff0e468db8, 0x340, 0x0, 0x7fff0e468d9f, 0x0) = 0xffffffffffffffda [0x7fff0e468ad8, 0]
proot info: vpid 47: sysenter start: newfstatat(0x3, 0x6f0000028954, 0x7fff0e468c40, 0x1000, 0x7f911fecdf30, 0x6f0000033220) = 0xffffffffffffffda [0x7fff0e468bb8, 0]
proot info: vpid 47: sysenter start: close(0x3, 0x6f0000028954, 0x7fff0e468c40, 0x1000, 0x7f911fecdf30, 0x6f0000033220) = 0xffffffffffffffda [0x7fff0e468bb8, 0]
proot info: vpid 47: sysenter start: writev(0x2, 0x7fff0e468900, 0xa, 0x20, 0x7fff0e468d48, 0x7f911fecdf30) = 0xffffffffffffffda [0x7fff0e4688c0, 0]
/nix/store/xdlpraypxdimjyfrr4k06narrv8nmfgh-nix-2.11.1/bin/nix-store: error while loading shared libraries: libsodium.so.23: cannot stat shared object: Invalid argument
proot info: vpid 47: sysenter start: exit_group(0x7f, 0x3c, 0x7f, 0x20, 0xe7, 0x7f911fecdf30) = 0xffffffffffffffda [0x7fff0e468d38, 0]
proot info: vpid 47: exited with status 127
Does that make any sense to you?
Well, I guess it's not really a proot issue;
$ LD_LIBRARY_PATH=pls/store/ga9q4ikprn36wm32gqm4k521iv9kic5p-libsodium-1.0.18/lib/ pls/store/scd5n7xsn0hh0lvhhnycr9gx0h8xfzsl-glibc-2.34-210/lib64/ld-linux-x86-64.so.2 pls/store/xdlpraypxdimjyfrr4k06narrv8nmfgh-nix-2.11.1/bin/nix-store
pls/store/xdlpraypxdimjyfrr4k06narrv8nmfgh-nix-2.11.1/bin/nix-store: error while loading shared libraries: libsodium.so.23: cannot stat shared object: Invalid argument
re log: yeah
IIRC strace has something like it for example
two libuv tests failed under proot but im not sure if its actually proot's fault
specifically fs_file_enametoolong and signal_multiple_loops
just mentioning it
Is this a proot issue?
ECC:
Ed25519 | nanosecs/iter cycles/iter
mult | Fatal: getentropy is not supported: Function not implemented
Hm ok seems like a kernel syscall interface issue I guess
hm
(old kernel)
Though I think this should be going through musl so it should work...hm...
I used a patch to musl to get a version of it
I'm running into some other issues now