Probably a good idea to cc: this to the kernel list :-)
I suspect it's intentional but with the planned changes for iptables
etc to be backed by bpf in the upstream kernel sometime in the future
it's likely going to need to be reviewed.
Peter
On Tue, Aug 7, 2018 at 10:25 PM, Timothée Ravier <tim(a)siosm.fr> wrote:
> Booting Fedora with Secure Boot enabled will result in Lockdown being enabled at boot
time. This will completly disable the BPF system call for all users [1][2].
>
> Unfortunately, this breaks the IPAddressAllow & IPAddressDeny systemd feature
[3][4][5].
>
> I don't have a solution for this, but as far as I understand, this will also
prevent other BPF use-cases (for example: Cilium on Fedora CoreOS).
>
> [1]
https://src.fedoraproject.org/rpms/kernel/blob/master/f/efi-lockdown.patc...
> [2]
https://git.kernel.org/pub/scm/linux/kernel/git/jforbes/linux.git/commit/...
> [3]
https://github.com/systemd/systemd/blob/master/src/core/bpf-firewall.c
> [4]
https://github.com/systemd/systemd/blob/master/NEWS#L1192
> [5]
https://www.freedesktop.org/software/systemd/man/systemd.resource-control...
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html
> List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...