diff options
| author | Vincent Haupert <mail@vincent-haupert.de> | 2022-08-21 12:22:16 +0200 |
|---|---|---|
| committer | Vincent Haupert <mail@vincent-haupert.de> | 2022-08-21 12:22:16 +0200 |
| commit | ca0120a4bcb759b9a9040219b1f0a5e5a86e34a1 (patch) | |
| tree | 434164dda59970a16033cb5d00164bac1a7161a4 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 495b19d5b3e62b4ec7e846bdfb6ef3d9c3b83492 (diff) | |
systemd: enable `BPF_FRAMEWORK` by default (`withLibBPF=true`)
So far, we have been building Systemd without `BPF_FRAMEWORK`. As a
result, some Systemd features like `RestrictNetworkInterfaces=` cannot
work. To make things worse, Systemd doesn't even complain when using a
feature which requires `+BPF_FRAMEWORK`; yet, the option has no effect:
# systemctl --version | grep -o "\-BPF_FRAMEWORK"
-BPF_FRAMEWORK
# systemd-run -t -p RestrictNetworkInterfaces="lo" ping -c 1 8.8.8.8
This commit enables `BPF_FRAMEWORK` by default. This is in line with
other distros (e.g., Fedora). Also note that BPF does not support stack
protector: https://lkml.org/lkml/2020/2/21/1000. To that end, I added a
small `CFLAGS` patch to the BPF building to keep using stack protector
as a default.
I also added an appropriate NixOS test.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions
