| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Add a basic test that simply makes sure pspax executes just fine, i.e.
doesn't get killed by the seccomp policy.
Signed-off-by: Mathias Krause <minipli@grsecurity.net>
Signed-off-by: Mike Gilbert <floppym@gentoo.org>
|
|
|
|
|
| |
Signed-off-by: Mike Frysinger <vapier@chromium.org>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
| |
This prevents new or unconventional systems requiring upstream changes,
though, this is not perfect, as it doesn't address some of the other
defines related to OSes the preprocessor does (namely, wrt the ldso
cache handling). I didn't touch these yet as I took a more conservative
approach of (probably) not changing what happens at runtime.
Signed-off-by: Arsen Arsenović <arsen@aarsen.me>
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some notes about the new build systems:
- I don't fully understand the testing system, but I think I understood
it well enough to implement an equivalent one.
- use_seccomp could be replaced by detecting seccomp support at runtime
(without support, Linux returns -EINVAL in include/linux/seccomp.h)
- The fuzzing test is broken and seems to have been for a while (see
commit 67f3ba64c91b5e1ac9fbbd0bc039fb8ca653cae1, it fails to fuzz on
my machine)
- make-tarball.sh has been replaced with meson dist - hopefully this
works. meson dist should also call seccomp-bpf.c to update
seccomp-bpf.h
Signed-off-by: Arsen Arsenović <arsen@aarsen.me>
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
| |
We use very little from it anymore, and can easily inline the few
things we want. This makes code work on non-Gentoo systems.
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
POSIX is adding the -E flag to enable ERE behavior, and GNU/sed already
supports this, as do various BSD systems (including OS X).
While GNU makes the suffix to -i optional, POSIX/etc... do not, so make
sure we always specify it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the ELF we're showing is linked directly against the ELF which is used
as the ELF interp (i.e. the ldso), make sure we don't list it twice.
We want to see it "twice" in the pretty form:
$ ./lddtree.py /bin/bash
/bin/bash (interpreter => /lib/ld-linux-armhf.so.3) <= here
libreadline.so.6 => /lib/libreadline.so.6
libncurses.so.5 => /lib/libncurses.so.5
libc.so.6 => /lib/libc.so.6
ld-linux-armhf.so.3 => /lib/ld-linux-armhf.so.3 <= here
But not in the list form (as that is used by scripts):
$ ./lddtree.py -l /bin/bash
/bin/bash
/lib/ld-linux-armhf.so.3 <= only here
/lib/libreadline.so.6
/lib/libncurses.so.5
/lib/libc.so.6
We also reconcile a few differences wrt interp display and the sh/py
implementations.
Reported-by: Tomasz Buchert <tomasz@debian.org>
|
|
|
|
|
|
|
|
| |
The functions.sh messes with PATH, so mangle it after we load it.
Pull out pass/fail so tests can use it directly.
Clean up the style of testit to be more bashy and safe (quotes).
|
| |
|
|
|
|
| |
URL: https://bugs.gentoo.org/413967
|
| |
|
|
|
|
| |
no non-GNU systems #507470 by Yuta SATOH
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|