On Mon, Jun 28, 2021 at 1:58 PM Thomas Weißschuh <linux@xxxxxxxxxxxxxx> wrote: > > Hi again! !!! :) > On Mo, 2021-06-28T13:34-0400, Paul Moore wrote: > > On Mon, Jun 28, 2021 at 1:13 PM Thomas Weißschuh <linux@xxxxxxxxxxxxxx> wrote: > > > On Mo, 2021-06-28T12:59-0400, Paul Moore wrote: > > > > On Mon, Jun 28, 2021 at 9:25 AM Thomas Weißschuh <linux@xxxxxxxxxxxxxx> wrote: ... > > Remember that seccomp filters are inherited across forks, so if your > > application loads an ABI specific filter and then fork()/exec()'s an > > application with a different ABI you could be in trouble. We saw this > > some years ago when people started running containers with ABIs other > > than the native system; if the container orchestrator didn't load a > > filter that knew about these non-native ABIs Bad Things happened. > > My application will not be able to spawn any new processes. > It is limited to write() and exit(). > Also this is a low-level system application so it should always be compiled for > the native ABI. > So this should not be an issue. > > > I'm sure you are already aware of libseccomp, but if not you may want > > to consider it for your application. Not only does it provide a safe > > and easy way to handle multiple ABIs in a single filter, it handles > > other seccomp problem areas like build/runtime system differences in > > the syscall tables/defines as well as the oddball nature of > > direct-call and multiplexed socket related syscalls, i.e. socketcall() > > vs socket(), etc. > > For a larger application this would be indeed my choice. > But for a small application like mine I don't think it is worth it. > libseccomp for example does provide a way to get the native audit arch: > `uint32_t seccomp_arch_native(void);`. It is implemented by ifdef-ing on > various compiler defines to detect the ABI compiled for. > > I'd like the kernel to provide this out-of-the box, so I don't have to have the > same ifdefs in my application(s) and keep them up to date. > > I found that the kernel internally already has a definition for my usecase: > SECCOMP_ARCH_NATIVE. > It is just not exported to userspace. I'm not sure that keeping the ifdefs up to date is going to be that hard, and honestly that is the right place to do it IMHO. The kernel can support any number of ABIs, but in the narrow use case you are describing in this thread you only care about the ABI of your own application; it doesn't sound like you really care about the kernel's ABI, but rather your application's ABI. > > I'm sorry, but I don't quite understand what you are looking for in > > the header files ... ? It might help if you could provide a concrete > > example of what you would like to see in the header files? > > I want to do something like the follwing inside my program to assemble a > seccomp filter that will be loaded before the error-prone parts of the > application will begin. > > 1: BPF_STMT(BPF_LD | BPF_W | BPF_ABS, syscall_arch), > 2: BPF_JUMP(BPF_JMP | BPF_JEQ | BPF_K, SECCOMP_ARCH_NATIVE, 0, $KILL) > 3: BPF_STMT(BPF_LD | BPF_W | BPF_ABS, syscall_nr), > 4: BPF_JUMP(BPF_JMP | BPF_JEQ | BPF_K, __NR_write, $ALLOW, $KILL), > > In line 4 I can already have the kernel headers provide me the correct syscall > number for the ABI my application is compiled for. > > For line 2 however I need to define AUDIT_ARCH_CURRENT on my own instead of > having a kernel header provide the correct value. -- paul moore www.paul-moore.com
